Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IteratorStep result == done cannot be passed to IteratorValue #21

Open
woess opened this issue Jan 16, 2025 · 0 comments
Open

IteratorStep result == done cannot be passed to IteratorValue #21

woess opened this issue Jan 16, 2025 · 0 comments

Comments

@woess
Copy link

woess commented Jan 16, 2025

In the following spec text, passing the result of IteratorStep to IteratorValue does not make sense, since if the iterator is done, the return value of IteratorStep is DONE, not the iterator result object expected by IteratorValue:

1. Let _iteratorResult_ be ? IteratorStep(_iteratorRecord_).
1. If _iteratorResult_ is ~done~, then
1. Perform ? IteratorValue(_iteratorResult_).

To fix this, IteratorStep probably has to be replaced with explicit IteratorNext and IteratorComplete calls.

@woess woess changed the title IteratorStep result == done should not be passed to IteratorValue IteratorStep result == done cannot be passed to IteratorValue Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant