rust/src/libcore/slice, branch stable

mv std libs to library/

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

Auto merge of #74510 - LukasKalbertodt:fix-range-from-index-panic, r=hanna-kruppe

2020-07-25T16:27:24+00:00

Fix panic message when `RangeFrom` index is out of bounds Before, the `Range` method was called with `end = slice.len()`. Unfortunately, because `Range::index` first checks the order of the indices (start has to be smaller than end), an out of bounds index leads to `core::slice::slice_index_order_fail` being called. This prints the message 'slice index starts at 27 but ends at 10', which is worse than 'index 27 out of range for slice of length 10'. This is not only useful to normal users reading panic messages, but also for people inspecting assembly and being confused by `slice_index_order_fail` calls. You can see the produced assembly [here](https://rust.godbolt.org/z/GzMGWf) and try on Playground [here](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=aada5996b2f3848075a6d02cf4055743). (By the way. this is only about which panic function is called; I'm pretty sure it does not improve anything about performance).

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

Slightly improve panic messages when range indices are out of bounds

2020-07-19T22:40:42+00:00

Fix panic message when `RangeFrom` index is out of bounds

2020-07-19T14:11:07+00:00

Before, the `Range` method was called with `end = slice.len()`. Unfortunately, because `Range::index` first checks the order of the indices (start has to be smaller than end), an out of bounds index leads to `core::slice::slice_index_order_fail` being called. This prints the message 'slice index starts at 27 but ends at 10', which is worse than 'index 27 out of range for slice of length 10'. This is not only useful to normal users reading panic messages, but also for people inspecting assembly and being confused by `slice_index_order_fail` calls.

Fix `Safety` docs for `from_raw_parts_mut`

2020-07-17T17:47:25+00:00

apply bootstrap cfgs

2020-07-16T23:36:49+00:00

Rollup merge of #73986 - RalfJung:raw-slice-as-ptr, r=sfackler

2020-07-14T14:39:00+00:00

add (unchecked) indexing methods to raw (and NonNull) slices This complements the existing (unstable) `len` method. Unfortunately, for non-null slices, we cannot call this method `as_ptr` as that overlaps with the existing method of the same name. If this looks reasonable to accept, I propose to reuse the https://github.com/rust-lang/rust/issues/71146 tracking issue and rename the feature get to `slice_ptr_methods` or so. Cc @SimonSapin Fixes https://github.com/rust-lang/rust/issues/60639

Optimize is_ascii for &str and &[u8]

2020-07-05T17:23:50+00:00