rust/src/liballoc/string.rs, branch 1.33.0

Remove licenses

2018-12-26T04:08:33+00:00

Fix typo

2018-12-09T21:10:20+00:00

Rollup merge of #56548 - Lucretiel:string-extend-optimize, r=sfackler

2018-12-06T06:49:01+00:00

Optimized string FromIterator + Extend impls I noticed that there was a lost opportunity to reuse string buffers in `FromIterator` and `FromIterator>`; updated the implementations to use these. In practice this translates to at least one fewer allocation when using these APIs. Additionally, rewrote `Extend` implementations to use `iter.for_each`, which (supposedly) helps the compiler optimize those loops (because iterator adapters are encouraged to provide optimized implementations of `fold` and `try_fold`.

Added explainatory comments

2018-12-06T01:46:03+00:00

Fixed mutability

2018-12-05T23:11:32+00:00

Optimized string FromIterator impls

2018-12-05T22:51:04+00:00

cleanup: remove static lifetimes from consts

2018-12-04T11:46:10+00:00

Update issue number of `shrink_to` methods to point the tracking issue

2018-12-02T07:08:08+00:00

String: add a FIXME to from_utf16

2018-11-21T09:17:54+00:00

Rollup merge of #55530 - ljedrz:speed_up_String_from_utf16, r=SimonSapin

2018-11-15T10:04:31+00:00

Speed up String::from_utf16 Collecting into a `Result` is idiomatic, but not necessarily fast due to rustc not being able to preallocate for the resulting collection. This is fine in case of an error, but IMO we should optimize for the common case, i.e. a successful conversion. This changes the behavior of `String::from_utf16` from collecting into a `Result` to pushing to a preallocated `String` in a loop. According to [my simple benchmark](https://gist.github.com/ljedrz/953a3fb74058806519bd4d640d6f65ae) this change makes `String::from_utf16` around **twice** as fast.