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

mv std libs to library/

2020-07-28T00:51:13+00:00

Document UTF-8 validity of String::from_raw_parts

2020-07-25T12:06:32+00:00

Fix wrong name in `String::from_raw_parts` docs

2020-07-25T12:04:56+00:00

Prefer type@str

2020-07-23T02:42:37+00:00

Make str point to primitive page

2020-07-23T02:37:17+00:00

Auto merge of #74010 - pierwill:pierwill-o-notation, r=GuillaumeGomez

2020-07-20T10:19:58+00:00

Use italics for O notation In documentation, I think it makes sense to italicize O notation (*O(n)*) as opposed to using back-ticks (`O(n)`). Visually, back-ticks focus the reader on the literal characters being used, making them ideal for representing code. Using italics, as far I can tell, more closely follows typographic conventions in mathematics and computer science. Just a suggestion, of course! 😇

Use italics for O notation

2020-07-20T04:43:39+00:00

Co-authored-by: Guillaume Gomez

Clarify the literal string

2020-07-19T05:42:11+00:00

Use intra-doc links in alloc::String

2020-07-18T18:03:44+00:00

Rollup merge of #72688 - djugei:master, r=Amanieu

2020-07-05T23:07:19+00:00

added .collect() into String from Box I have not created an rfc, because i felt like this is a very minor change. i have just set a random feature name and rust version as stability attribute, i expect to have to change that, i just don't know what the policy on that is. all guides i could find focused on contributing to the compiler, not contributing to the standard library. drawbacks: more code in the standard library, could be replaced with specialization: base-implementation for AsRef\ and specialization for String and Cow. i can write that code if ppl want it. advantages: using "real strings" i.e. Box\ is as ergonomic as string slices (&str) and string buffers (String) with iterators.