[6.1] [stdlib] Unicode 16 #78804
Merged
[6.1] [stdlib] Unicode 16 #78804
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
Contributor
Azoy
commented
Jan 22, 2025
Azoy
commented
- Explanation: This updates the data tables in the stdlib to support the recent Unicode 16 version as well as make changes to the opaque stdlib grapheme breaking algorithm to support changes in their breaking rules.
- Scope: Standard library's unicode data tables and grapheme breaking algorithm.
- Issues: N/A
- Original PRs: [stdlib] Unicode 16 #78664
- Risk: Low. All of the changes are internal stdlib implementation details that do not affect source or ABI.
- Testing: Updated the tests with the new Unicode provided tests for all data and breaking rules and this change passes all such tests.
- Reviewers: N/A
[stdlib] Unicode 16
|
@swift-ci please test |
|
cc @parkera |
stephentyrone
approved these changes
Feb 12, 2025
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.