Make unicode-property-data ecmaVersion-aware #798
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also, make it use regular expressions à la keywords, and update test262 again.
TimothyGu
changed the title
|
Nice, thanks! |
This was referenced Jul 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The data in unicode-property-data should not be taken to mirror Unicode properties directly, but rather individual editions of ECMAScript have their own allowed property names and values. For instance, the latest ES draft adds the
Extended_Pictographicbinary property and a series ofScriptproperty values to keep up with Unicode 11.0.0 as compared to ES 9, but when the user requests ES 9 the additions should not be allowed.Also, make the entire system use regular expressions à la keywords, and update test262 again.