diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2020-04-24 02:47:32 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-24 02:47:32 +0200 |
| commit | c33deb9fda9558d4c46201cddbe2a89ede78082b (patch) | |
| tree | c75609be67deb7f722c653ec7ce5b2b9146e8b1e /src/libcore | |
| parent | 9ff020e0dd73cd8a64711bf999f69970ec608718 (diff) | |
| parent | aa0175c98d0530b32a80542aaf9dab1be03dbb2b (diff) | |
Rollup merge of #71068 - pyfisch:unicode-version-stable, r=SimonSapin
Stabilize UNICODE_VERSION (feature unicode_version) Tracking issue: #49726 r? @sfackler #71020 changed the definition of `UNICODE_VERSION` just 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
Diffstat (limited to 'src/libcore')
| -rw-r--r-- | src/libcore/char/mod.rs | 4 | ||||
| -rw-r--r-- | src/libcore/unicode/mod.rs | 7 |
2 files changed, 7 insertions, 4 deletions
diff --git a/src/libcore/char/mod.rs b/src/libcore/char/mod.rs index 715ad8992ad..d82a482e0f1 100644 --- a/src/libcore/char/mod.rs +++ b/src/libcore/char/mod.rs @@ -34,9 +34,7 @@ pub use self::convert::ParseCharError; pub use self::convert::{from_digit, from_u32}; #[stable(feature = "decode_utf16", since = "1.9.0")] pub use self::decode::{decode_utf16, DecodeUtf16, DecodeUtf16Error}; - -// unstable re-exports -#[unstable(feature = "unicode_version", issue = "49726")] +#[stable(feature = "unicode_version", since = "1.45.0")] pub use crate::unicode::UNICODE_VERSION; use crate::fmt::{self, Write}; diff --git a/src/libcore/unicode/mod.rs b/src/libcore/unicode/mod.rs index 3952ae4482e..28c07f77170 100644 --- a/src/libcore/unicode/mod.rs +++ b/src/libcore/unicode/mod.rs @@ -7,9 +7,14 @@ mod unicode_data; /// The version of [Unicode](http://www.unicode.org/) that the Unicode parts of /// `char` and `str` methods are based on. /// +/// New versions of Unicode are released regularly and subsequently all methods +/// in the standard library depending on Unicode are updated. Therefore the +/// behavior of some `char` and `str` methods and the value of this constant +/// changes over time. This is *not* considered to be a breaking change. +/// /// The version numbering scheme is explained in /// [Unicode 11.0 or later, Section 3.1 Versions of the Unicode Standard](https://www.unicode.org/versions/Unicode11.0.0/ch03.pdf#page=4). -#[unstable(feature = "unicode_version", issue = "49726")] +#[stable(feature = "unicode_version", since = "1.45.0")] pub const UNICODE_VERSION: (u8, u8, u8) = unicode_data::UNICODE_VERSION; // For use in liballoc, not re-exported in libstd. |