Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: a9b3c904d0bb7d3cb52b1b2758128726156be870
https://github.com/WebKit/WebKit/commit/a9b3c904d0bb7d3cb52b1b2758128726156be870
Author: Sosuke Suzuki <[email protected]>
Date: 2025-02-27 (Thu, 27 Feb 2025)
Changed paths:
A JSTests/stress/iterator-from-null-checks.js
M JSTests/test262/expectations.yaml
M Source/JavaScriptCore/builtins/WrapForValidIteratorPrototype.js
Log Message:
-----------
[JSC] `%WrapForValidIteratorPrototype%.return` should not throw `TypeError`
when underlying iterator's `return` method is null
https://bugs.webkit.org/show_bug.cgi?id=288714
Reviewed by Yusuke Suzuki.
According to the spec[1], `%WrapForValidIteratorPrototype%.return`
returns `{ done: true, value: undefined }` if the underlying
iterator's `return` method is `null` or `undefined`.
However, our JSC throws `TypeError` if the underlying iterator's
`return` method is `null`.
This patch fixes it to comply with the spec.
[1]: https://tc39.es/ecma262/#sec-%wrapforvaliditeratorprototype%.return
* JSTests/test262/expectations.yaml:
* Source/JavaScriptCore/builtins/WrapForValidIteratorPrototype.js:
(return):
Canonical link: https://commits.webkit.org/291302@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-changes
