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

re-use IteratorResult objects when possible #18

Merged
merged 1 commit into from
Dec 2, 2024
Merged

Conversation

michaelficarra
Copy link
Member

Fixes #17.

@michaelficarra
Copy link
Member Author

In plenary today, we decided to do this. Merging.

@michaelficarra michaelficarra merged commit b1d267c into main Dec 2, 2024
2 checks passed
@michaelficarra michaelficarra deleted the GH-17 branch December 2, 2024 21:01
michaelficarra added a commit to anba/test262 that referenced this pull request Dec 2, 2024
@anba
Copy link

anba commented Dec 2, 2024

This needs IteratorValue when done to match yield*, right?

@michaelficarra
Copy link
Member Author

@anba PR here: #19

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.

re-use (done: false) IteratorResult objects yielded by underlying iterator
2 participants