summary refs log tree commit diff
path: root/src/libstd_unicode/char.rs
AgeCommit message (Collapse)AuthorLines
2018-01-15Reexport -> re-export in prose and documentation commentsCarol (Nichols || Goulding)-2/+2
2018-01-02Move static code outside of unciode.py.Clar Charr-1/+3
2017-12-12Auto merge of #46411 - rillian:str_ascii, r=kennytmbors-6/+6
Mark ascii methods on primitive types stable in 1.23.0 not 1.21.0. The ascii_methods_on_intrinsics feature stabilization didn't land in time for 1.21.0. Update the annotation so the documentation is correct about when these methods became available.
2017-12-09Use Try syntax for Option in place of macros or matchMatt Brubeck-6/+1
2017-12-03Rollup merge of #46432 - tromey:doc-fix-46307, r=estebankCorey Farwell-1/+1
Fix documentation for DecodeUtf16Error Fixes #46307
2017-12-02Mark ascii methods on primitive types stable in 1.23.0.Ralph Giles-6/+6
The ascii_methods_on_intrinsics feature stabilization didn't land in time for 1.21.0. Update the annotation so the documentation is correct about when these methods became available.
2017-12-01Fix documentation for DecodeUtf16ErrorTom Tromey-1/+1
Fixes #46307
2017-11-29Rollup merge of #46077 - LukasKalbertodt:stabilize-ascii-ctype, r=alexcrichtonkennytm-10/+10
Stabilize some `ascii_ctype` methods As discussed in #39658, this PR stabilizes those methods for `u8` and `char`. All inherent `ascii_ctype` for `[u8]` and `str` are removed as we prefer the more explicit version `s.chars().all(|c| c.is_ascii_())`. This PR doesn't modify the `AsciiExt` trait. There, the `ascii_ctype` methods are still unstable. It is planned to remove those in the future (I think). I had to modify some code in `ascii.rs` to properly implement `AsciiExt` for all types. Fixes #39658.
2017-11-28Change `since` attribute from ctype methods from 1.23 to 1.24Lukas Kalbertodt-10/+10
The changes didn't land in time for 1.23 and stabilizations won't be backported to beta.
2017-11-22Add missing Debug impls to std_unicodeOliver Middleton-1/+4
Also adds #![deny(missing_debug_implementations)] so they don't get missed again.
2017-11-18Stabilize `ascii_ctype` methods for `u8` and `char`Lukas Kalbertodt-10/+10
The feature of those methods was renamed to "ascii_ctype_on_intrinsics".
2017-11-14Fixed several pulldown warnings when documenting libstd.kennytm-1/+1
2017-11-03Mark several ascii methods as unstable againLukas Kalbertodt-10/+30
We don't want to stabilize them now already. The goal of this set of commits is just to add inherent methods to the four types. Stabilizing all of those methods can be done later.
2017-11-03Fix lists in doc comments for ascii methods of u8 and charLukas Kalbertodt-2/+4
2017-11-03Copy `AsciiExt` methods to `char` directlyLukas Kalbertodt-0/+501
This is done in order to deprecate AsciiExt eventually.
2017-09-18[libstd_unicode] Expose UnicodeVersion typeBehnam Esfahbod-1/+1
In <https://github.com/rust-lang/rust/pull/42998>, we added an uninstantiable type for the internal `UNICODE_VERSION` value, `UnicodeVersion`, but it was not made public to the outside of the crate, resulting in the value becoming less useful. Here we make the type accessible from the outside. Also add a run-pass test to make sure the type and value can be accessed as intended.
2017-07-25std: Stabilize `char_escape_debug`Alex Crichton-4/+1
Stabilizes: * `<char>::escape_debug` * `std::char::EscapeDebug` Closes #35068
2017-07-10Correct some stability attributesOliver Middleton-1/+1
These show up in rustdoc so need to be correct.
2017-06-20Rollup merge of #42271 - tinaun:charfromstr, r=alexcrichtonCorey Farwell-0/+2
add `FromStr` Impl for `char` fixes #24939. is it possible to use pub(restricted) instead of using a stability attribute for the internal error representation? is it needed at all?
2017-06-20added `FromStr` Impl for `char`tinaun-0/+2
2017-06-16Introduce tidy lint to check for inconsistent tracking issuesest31-4/+4
This commit * Refactors the collect_lib_features function to work in a non-checking mode (no bad pointer needed, and list of lang features). * Introduces checking whether unstable/stable tags for a given feature have inconsistent tracking issues. * Fixes such inconsistencies throughout the codebase.
2017-03-25char::to_uppercase doc typo: use the 'an' article.Colin Wallace-1/+1
2017-03-25char::to_uppercase doc typo: s/lowercase/uppercase/Colin Wallace-1/+1
2017-03-17Rollup merge of #40499 - ericfindlay:master, r=steveklabnikCorey Farwell-2/+4
Corrected very minor documentation detail about Unicode and Japanese Japanese half-width and full-width romaji characters do have upper and lowercase according Unicode (but other Japanese characters do not). For example, ` assert_eq!('\u{FF21}'.to_lowercase().collect::<String>(),"\u{FF41}");` r? @steveklabnik
2017-03-15Ammended minor documentation detail abour Unicode cases.Eric Findlay-2/+4
2017-03-13Remove function invokation parens from documentation links.Corey Farwell-7/+7
This was never established as a convention we should follow in the 'More API Documentation Conventions' RFC: https://github.com/rust-lang/rfcs/blob/master/text/1574-more-api-documentation-conventions.md
2017-03-14Corrected very minor documentation detail about Unicode and JapaneseEric Findlay-2/+2
2017-01-29Fix a few impl stability attributesOliver Middleton-3/+2
The versions show up in rustdoc.
2017-01-11Implement Display for char Escape*, To*case.Clar Charr-49/+150
2016-12-16Address falloutAaron Turon-2/+0
2016-12-15Stabilize std::char::{encode_utf8, encode_utf16}Aaron Turon-10/+2
2016-11-30Rename 'librustc_unicode' crate to 'libstd_unicode'.Corey Farwell-0/+977
Fixes #26554.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-25 22:23:37 +0000