support Unicode 15 via utf8proc 2.8 #47392
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
KristofferC
pushed a commit
that referenced
this pull request
Oct 23, 2023
Similar to #47392, support [Unicode 15.1](https://www.unicode.org/versions/Unicode15.1.0/) by bumping utf8proc to 2.9.0 (JuliaStrings/utf8proc#253). This allows us to use [118 exciting new emoji characters](https://blog.emojipedia.org/whats-new-in-unicode-15-1-and-emoji-15-1/) as identifiers, including "edible mushroom" `"\U1f344\u200d\U1f7eb"` (but still no superscript "q"). Interestingly, they also updated the [Unicode recommendations on programming-language identifiers (UAX#31)](https://www.unicode.org/reports/tr31/tr31-39.html#Mathematical_Compatibility_Notation_Profile) to finally "bless" identifiers beginning with `∂` and `∇` and/or ending with numeric sub/superscripts. They still don't recommend nearly the range of identifiers accepted by Julia, however.
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.
Similarly to #43443, support Unicode 15 by bumping utf8proc to 2.8.0 (which has no other significant changes).