diff options
| author | bors <bors@rust-lang.org> | 2018-09-16 07:22:24 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-09-16 07:22:24 +0000 |
| commit | f4819878cd4e397cc3fff9679e3255af1adb2430 (patch) | |
| tree | 0dcf6516b7116891afd47811bac079c4eef53b4b /src/libsyntax/parse | |
| parent | e4ba1d41e3c2a66215943e43de70f93bb195b1f0 (diff) | |
| parent | f4f114002e2a39494674107eb307770fffe33e95 (diff) | |
| download | rust-f4819878cd4e397cc3fff9679e3255af1adb2430.tar.gz rust-f4819878cd4e397cc3fff9679e3255af1adb2430.zip | |
Auto merge of #53754 - RalfJung:slice_align_to, r=alexcrichton
stabilize slice_align_to This is very hard to implement correctly, and leads to [serious bugs](https://github.com/llogiq/bytecount/pull/42) when done incorrectly. Moreover, this is needed to be able to run code that opportunistically exploits alignment on miri. So code using `align_to`/`align_to_mut` gets the benefit of a well-tested implementation *and* of being able to run in miri to test for (some kinds of) UB. This PR also clarifies the guarantee wrt. the middle part being as long as possible. Should the docs say under which circumstances the middle part could be shorter? Currently, that can only happen when running in miri.
Diffstat (limited to 'src/libsyntax/parse')
0 files changed, 0 insertions, 0 deletions