Uh oh!
There was an error while loading. Please reload this page.
Stabilize UNICODE_VERSION (feature unicode_version) - #71068
Conversation
Serentty
commented
Apr 12, 2020
Using a |
sfackler
commented
Apr 12, 2020
@Serentty the version numbers are defined by the standard to always be one byte each: #49726 (comment). |
sfackler
commented
Apr 12, 2020
@rfcbot fcp merge |
Team member @sfackler has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
Serentty
commented
Apr 12, 2020
@sfackler I should have checked to see if there was anything like that before commenting. This seems like a perfect solution then. |
rfcbot
commented
Apr 13, 2020
🔔 This is now entering its final comment period, as per the review above. 🔔 |
Mark-Simulacrum
commented
Apr 13, 2020
I would like to see an explicit note in the documentation that says something about this version number changing over time, and that the value is as such not covered by our stability policy. |
pyfisch
commented
Apr 13, 2020
@Mark-Simulacrum I've added a note explaining that Rust regularly updates to the most recent Unicode version and that therefore the version number will change. |
rfcbot
commented
Apr 23, 2020
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. The RFC will be merged soon. |
There was a problem hiding this comment.
Beta has branched to 1.44: https://github.com/rust-lang/rust/blob/beta/src/bootstrap/channel.rs#L15-L16
So this needs to be 1.45.0, same with the const item below. r=me with this.
The feature will become stable in Rust 1.45. Noted that the value of UNICODE_VERSION is expected to change.
pyfisch
commented
Apr 23, 2020
Changed version to 1.45 and squashed everything into one commit. r? @SimonSapin |
SimonSapin
commented
Apr 23, 2020
Looks good, thanks! @bors r+ |
bors
commented
Apr 23, 2020
📌 Commit aa0175c has been approved by |
Rollup of 6 pull requests Successful merges: - rust-lang#70845 (Make the `structural_match` error diagnostic for const generics clearer) - rust-lang#71063 (Document unsafety in core::{option, hash}) - rust-lang#71068 (Stabilize UNICODE_VERSION (feature unicode_version)) - rust-lang#71426 (fix error code in E0751.md) - rust-lang#71459 (Add leading 0x to offset in Debug fmt of Pointer) - rust-lang#71492 (Document unsafety in core::{panicking, alloc::layout, hint, iter::adapters::zip}) Failed merges: r? @ghost
Serentty
commented
Apr 24, 2020
Yay! This is perfect for static asserts in software that needs a certain new version of Unicode. |
Tracking issue: #49726
r? @sfackler
#71020 changed the definition of
UNICODE_VERSIONjust yesterday from a struct to a tuple. Maybe you want to wait some more before stabilizing this constant, on the other hand this is a very small and simple addition.CC @behnam@SimonSapin@Serentty