diff options
| author | Ralf Jung <post@ralfj.de> | 2020-05-21 21:10:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-21 21:10:41 +0200 |
| commit | 261505a0cf7a946fc2e5e8ed84f58e93b871f27b (patch) | |
| tree | 6b418996fa36697c71ddcd60233ec1de710c3505 /src/test/incremental/thinlto | |
| parent | 3d5f130aae7554ceaf0601979d0aeb9fc593cbb0 (diff) | |
| parent | 67e075589b7e19a87130a700b7e59015a1b80f11 (diff) | |
| download | rust-261505a0cf7a946fc2e5e8ed84f58e93b871f27b.tar.gz rust-261505a0cf7a946fc2e5e8ed84f58e93b871f27b.zip | |
Rollup merge of #72350 - danielhenrymantilla:doc_warn_against_adjacent_slice_concat, r=RalfJung
Improve documentation of `slice::from_raw_parts` This is to provide a more explicit statement against a code pattern that many people end up coming with, since the reason of it being unsound comes from the badly known single-allocation validity rule. Providing that very pattern as a counter-example could help mitigate that. See also: https://internals.rust-lang.org/t/pre-rfc-add-join-seq-method-to-slices-and-strs/11936/13 r? @RalfJung
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions