-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Normative: add RegExp Match Indices #1713
Conversation
d2b0589
to
ba92766
Compare
Test262 Tests have already been merged: tc39/test262#2309 |
I've submitted an editorial PR against this PR's branch. |
Editorial tweaks re PR tc39#1713
This has now been completed. |
48f9a15
to
683300e
Compare
@ljharb, I know you approved this prior to the addition of the |
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.
still LGTM
9958ad7
to
3d1c29c
Compare
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.
LGTM otherwise.
58e18b7
to
97c1679
Compare
@rbuckton I've rebased your PR and applied my editorial changes. |
1. Assert: _match_.[[StartIndex]] is an integer value ≥ 0 and < the length of _S_. | ||
1. Assert: _match_.[[EndIndex]] is an integer value ≥ _match_.[[StartIndex]] and ≤ the length of _S_. | ||
1. Return ! CreateArrayFromList(« 𝔽(_match_.[[StartIndex]]), 𝔽(_match_.[[EndIndex]]) »). | ||
1. Assert: _match_.[[StartIndex]] is a non-negative integer less than or equal to the length of _S_. |
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.
This was totally on purpose and not an accident.
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.
Not against its being in prose, but what was the reasoning here and above?
1. Assert: _match_.[[StartIndex]] is an integer value ≥ 0 and < the length of _S_. | ||
1. Assert: _match_.[[EndIndex]] is an integer value ≥ _match_.[[StartIndex]] and ≤ the length of _S_. | ||
1. Return ! CreateArrayFromList(« 𝔽(_match_.[[StartIndex]]), 𝔽(_match_.[[EndIndex]]) »). | ||
1. Assert: _match_.[[StartIndex]] is a non-negative integer less than or equal to the length of _S_. |
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.
Not against its being in prose, but what was the reasoning here and above?
efc369b
to
0209d85
Compare
PR tc39#1713 changed the signature of the Abstract Closure created+returned by CompilePattern, but didn't make the corresponding change to the return-type in the section heading.
PR tc39#1713 changed the signature of the Abstract Closure created+returned by CompilePattern, but didn't make the corresponding change to the return-type in the section heading.
This adds the specification text from https://github.com/tc39/proposal-regexp-match-indices, currently at Stage 3.