diff options
| author | Yuki Okushi <huyuumi.dev@gmail.com> | 2019-12-12 10:09:15 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-12-12 10:09:15 +0900 |
| commit | 9860a4eeb7e555b3a137b2aa0cde818d44a608dc (patch) | |
| tree | 63fa6f6d98f486d8da906e4b12daa91f35efb2d2 /src/test/debuginfo/enum-thinlto.rs | |
| parent | 27d6f55f47e8875e71083a28ed84ea5a88e1b596 (diff) | |
| parent | fafa4897985f932490960e90ddd2ff39134e967e (diff) | |
| download | rust-9860a4eeb7e555b3a137b2aa0cde818d44a608dc.tar.gz rust-9860a4eeb7e555b3a137b2aa0cde818d44a608dc.zip | |
Rollup merge of #62514 - stephaneyfx:box-ffi, r=nikomatsakis
Clarify `Box<T>` representation and its use in FFI This officializes what was only shown as a code example in [the unsafe code guidelines](https://rust-lang.github.io/unsafe-code-guidelines/layout/function-pointers.html?highlight=box#use) and follows [the discussion](https://github.com/rust-lang/unsafe-code-guidelines/issues/157) in the corresponding repository. It is also related to [the issue](https://github.com/rust-lang/rust/issues/52976) regarding marking `Box<T>` `#[repr(transparent)]`. If the statement this PR adds is incorrect or a more in-depth discussion is warranted, I apologize. Should it be the case, the example in the unsafe code guidelines should be amended and some document should make it clear that it is not sound/supported.
Diffstat (limited to 'src/test/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions