1ad218f3af
As our implementation of MCP411 nears completion and we begin to solicit testing, it's no longer reasonable to expect testers to type or remember `BikeshedIntrinsicFrom`. The name degrades the ease-of-reading of documentation, and the overall experience of using compiler safe transmute. Tentatively, we'll instead adopt `TransmuteFrom`. This name seems to be the one most likely to be stabilized, after discussion on Zulip [1]. We may want to revisit the ordering of `Src` and `Dst` before stabilization, at which point we'd likely consider `TransmuteInto` or `Transmute`. [1] https://rust-lang.zulipchat.com/#narrow/stream/216762-project-safe-transmute/topic/What.20should.20.60BikeshedIntrinsicFrom.60.20be.20named.3F
45 lines
1.0 KiB
Rust
45 lines
1.0 KiB
Rust
//! The variants of an enum must be padded with uninit bytes such that they have
|
|
//! the same length (in bytes).
|
|
|
|
#![crate_type = "lib"]
|
|
#![feature(transmutability)]
|
|
#![allow(dead_code)]
|
|
|
|
mod assert {
|
|
use std::mem::{Assume, TransmuteFrom};
|
|
|
|
pub fn is_transmutable<Src, Dst>()
|
|
where
|
|
Dst: TransmuteFrom<Src, {
|
|
Assume::ALIGNMENT
|
|
.and(Assume::LIFETIMES)
|
|
.and(Assume::SAFETY)
|
|
.and(Assume::VALIDITY)
|
|
}>
|
|
{}
|
|
}
|
|
|
|
#[derive(Clone, Copy)]
|
|
#[repr(C)] struct Zst;
|
|
|
|
#[derive(Clone, Copy)]
|
|
#[repr(u8)] enum V0 { V = 0 }
|
|
|
|
#[derive(Clone, Copy)]
|
|
#[repr(u8)] enum V2 { V = 2 }
|
|
|
|
#[repr(C, u8)]
|
|
enum Lopsided {
|
|
Smol(Zst),
|
|
Lorg(V0),
|
|
}
|
|
|
|
#[repr(C)] struct Src(V0, Zst, V2);
|
|
#[repr(C)] struct Dst(Lopsided, V2);
|
|
|
|
fn should_pad_variants() {
|
|
// If the implementation (incorrectly) fails to pad `Lopsided::Smol` with
|
|
// an uninitialized byte, this transmutation might be (wrongly) accepted:
|
|
assert::is_transmutable::<Src, Dst>(); //~ ERROR cannot be safely transmuted
|
|
}
|