about summary refs log tree commit diff
path: root/src/rustllvm/ExecutionEngineWrapper.cpp
diff options
context:
space:
mode:
authorManish Goregaokar <manishsmail@gmail.com>2015-03-18 14:38:56 +0530
committerManish Goregaokar <manishsmail@gmail.com>2015-03-18 22:21:06 +0530
commit181441cf6632ad34f73bd52fc0e6246981cdb378 (patch)
tree3dc301cfc13445829b50200d1bf442c60c7d91a9 /src/rustllvm/ExecutionEngineWrapper.cpp
parent46f649c479ce40f3b4590590dda6c2895e8d60f6 (diff)
parentaa88da63179b8ccd3b809e98b489c25199b06cf7 (diff)
downloadrust-181441cf6632ad34f73bd52fc0e6246981cdb378.tar.gz
rust-181441cf6632ad34f73bd52fc0e6246981cdb378.zip
Rollup merge of #23461 - alexcrichton:feat-char-at, r=aturon
 This commit clarifies some of the unstable features in the `str` module by
moving them out of the blanket `core` and `collections` features.

The following methods were moved to the `str_char` feature which generally
encompasses decoding specific characters from a `str` and dealing with the
result. It is unclear if any of these methods need to be stabilized for 1.0 and
the most conservative route for now is to continue providing them but to leave
them as unstable under a more specific name.

* `is_char_boundary`
* `char_at`
* `char_range_at`
* `char_at_reverse`
* `char_range_at_reverse`
* `slice_shift_char`

The following methods were moved into the generic `unicode` feature as they are
specifically enabled by the `unicode` crate itself.

* `nfd_chars`
* `nfkd_chars`
* `nfc_chars`
* `graphemes`
* `grapheme_indices`
* `width`
Diffstat (limited to 'src/rustllvm/ExecutionEngineWrapper.cpp')
0 files changed, 0 insertions, 0 deletions