-
Notifications
You must be signed in to change notification settings - Fork 475
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
add tests for "iterator helpers close receiver on argument validation failure" #4350
Conversation
test/built-ins/Iterator/prototype/take/argument-validation-failure-closes-underlying.js
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementing this normative change is likely to cause https://github.com/tc39/test262/blob/main/test/built-ins/Iterator/prototype/reduce/non-callable-reducer.js to start failing, because the underlying iterator will already be closed during the second call to reduce
.
Thanks for the review @sosukesuzuki, addressed comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Two comments, but they apply to multiple files.
test/built-ins/Iterator/prototype/drop/argument-validation-failure-closes-underlying.js
Show resolved
Hide resolved
test/built-ins/Iterator/prototype/drop/argument-validation-failure-closes-underlying.js
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
652ac6c
to
7722e98
Compare
Tests for tc39/ecma262#3467, which has consensus and is just waiting for tests.
No existing tests were invalidated as far as I can tell (presumably because if we'd thought to test this behavior then we'd have updated the proposal instead of needing the PR).