You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
woess
changed the title
IteratorStep result == done should not be passed to IteratorValue
IteratorStep result == done cannot be passed to IteratorValue
Jan 16, 2025
In the following spec text, passing the result of
IteratorStep
toIteratorValue
does not make sense, since if the iterator is done, the return value ofIteratorStep
is DONE, not the iterator result object expected byIteratorValue
:proposal-iterator-sequencing/spec.emu
Lines 28 to 30 in 5731124
To fix this,
IteratorStep
probably has to be replaced with explicitIteratorNext
andIteratorComplete
calls.The text was updated successfully, but these errors were encountered: