/ecma262

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

[Informative] Observable changes because of Unicode 10 #937

Closed
mathiasbynens opened this Issue Jun 21, 2017 · 1 comment

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
No milestone
1 participant
@mathiasbynens
@mathiasbynens
Member

mathiasbynens commented Jun 21, 2017 •
edited

Output of node compare.js:

Comparing Unicode v10.0.0 to Unicode v9.0.0…
Binary_Property/ID_Start: 0 removals
Binary_Property/ID_Start: 8,327 new code points
Binary_Property/ID_Continue: 0 removals
Binary_Property/ID_Continue: 8,417 new code points
General_Category/Space_Separator: 0 removals
General_Category/Space_Separator: 0 new code points
Case_Folding=S: 0 removals
Case_Folding=S: 0 new code points
Case_Folding=F: 0 removals
Case_Folding=F: 0 new code points

(Do any other properties need checking?)

TL;DR As far as ECMAScript is concerned, the implicit update to Unicode 10 causes no backwards-incompatible changes — it only enables some new identifier symbols. 👍
@mathiasbynens

This comment has been minimized.

Show comment
Hide comment
@mathiasbynens

mathiasbynens Jun 21, 2017

Member

Closing this issue as it’s purely informative.

Let me know if any other Unicode properties need comparing.
Member

mathiasbynens commented Jun 21, 2017 •
edited

Closing this issue as it’s purely informative.

Let me know if any other Unicode properties need comparing.

@mathiasbynens mathiasbynens closed this Jun 21, 2017

@mathiasbynens mathiasbynens added the unicode label Jun 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment