-
Notifications
You must be signed in to change notification settings - Fork 478
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
Async-from-sync test the iterator closes when .throw() is undefined #3976
Async-from-sync test the iterator closes when .throw() is undefined #3976
Conversation
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-null.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-null.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-get-return-undefined.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-get-return-undefined.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-get-return-undefined.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-poisoned-return.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-return-not-object.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-return-object.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-return-object.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-return-object.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined.js
Outdated
Show resolved
Hide resolved
Thank you @nicolo-ribaudo and @ljharb for the review and suggestions! |
@Ms2ger Re: the label: the PR to the specification has had approval for ~2 years and is only waiting on these tests to land (i.e. it's conceptually "stage 3"). If you're just waiting on the specification, and these are otherwise ready to land, they should be landed, I think. We can land the spec PR first if necessary, but I don't want to do that until the tests are actually ready to land. |
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.
I did not check these line by line against the normative change. So it would be nice-to-have if someone more familiar with that change would take a look. Even without that, I think the use of engine262 gives sufficient confidence and I would be fine with landing it as is.
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-null.js
Outdated
Show resolved
Hide resolved
test/built-ins/AsyncFromSyncIteratorPrototype/throw/throw-undefined-get-return-undefined.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.
👍
Testing normative changes of ecma626 PR 2600
These test paths from newly added call to IteratorClose in step 7.c of %AsyncFromSyncIteratorPrototype%.throw as per normative changes of ecma626 PR 2600
Co-authored-by: Jordan Harband <[email protected]>
72f2345
to
216e3c3
Compare
All comments have been addressed and no new ones have shown up since last week, let's let this train leave the station! 😄 |
This adds tests for the normative changes in tc39/ecma262#2600 for the new steps in
%AsyncFromSyncIteratorPrototype%.throw
, also modifying two existing tests.These tests have been tested with this PR of engine262, which implements the normative changes: engine262/engine262#230
Partly fixes #3387