Skip to content

Conversation

michaelficarra
Copy link
Member

These tests should match the spec changes in tc39/proposal-iterator-sequencing#26.

@michaelficarra michaelficarra requested a review from a team as a code owner June 20, 2025 02:34
@Ms2ger Ms2ger force-pushed the iterator-sequencing-may-updates branch from bdb051f to 29c5f67 Compare August 22, 2025 14:03
@Ms2ger Ms2ger enabled auto-merge (rebase) August 22, 2025 14:04
@Ms2ger Ms2ger merged commit b947715 into main Aug 22, 2025
15 checks passed
@Ms2ger Ms2ger deleted the iterator-sequencing-may-updates branch August 22, 2025 14:06
@iamstolis
Copy link
Contributor

Shouldn't built-ins/Iterator/concat/next-method-returns-throwing-value.js be updated as well? iterator.next() did not throw before because iteratorResult was reused (i.e. its value was not read). Now, IteratorStepValue() always reads the value of the inner iterator (which throws in this case). So, iterator.next() should throw now, right?

In other words, I think that 71794b1 should be reverted now.

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

Successfully merging this pull request may close these issues.

4 participants