-
Notifications
You must be signed in to change notification settings - Fork 479
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 not calling well-known symbols on primitives for string methods #4404
base: main
Are you sure you want to change the base?
Add tests for not calling well-known symbols on primitives for string methods #4404
Conversation
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.
generally seems good overall
test/built-ins/String/prototype/match/cstm-matcher-on-bigint-primitive.js
Show resolved
Hide resolved
test/built-ins/String/prototype/match/cstm-matcher-on-boolean-primitive.js
Show resolved
Hide resolved
test/built-ins/String/prototype/match/cstm-matcher-on-number-primitive.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.
for Symbol.match, what about new RegExp
?
The normative PR does not change the behaviour of the regexp constructor. It already only gets |
aha, then the normative PR has an even stronger case in favor of it :-) |
See tc39/ecma262#3009