Claim to follow Unicode 16 for lexing identifiers. #557
Conversation
This file contains hidden or 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
This change happened in Rust 1.83.
|
cc @Veykril |
|
The changelog (as used so far) generally only tracks the language level changes from the RELEASES.md, so if that was not listed there it doesn't need to touch the changelog I believe. |
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.
Rustc has used Unicode 16 since Rust 1.83.
This change brings the FLS into sync with the Reference for this detail.
See rust-lang/reference#1688.
I'm not sure whether the changelog should be updated (and if so, how). The FLS was previously claiming Unicode version 13. I don't have notes saying which versions the updates to Unicode 14 and 15 happened in.
Unicode normalization is also dependent on the Unicode version, but there's no version number in the existing text of §2.3:16 (
fls_vde7gev5rz4q).