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
44 lines
1023 B
Rust
44 lines
1023 B
Rust
#![crate_type = "lib"]
|
|
#![feature(transmutability)]
|
|
#![allow(dead_code, incomplete_features, non_camel_case_types)]
|
|
|
|
use std::mem::MaybeUninit;
|
|
|
|
mod assert {
|
|
use std::mem::{Assume, TransmuteFrom};
|
|
|
|
pub fn is_maybe_transmutable<Src, Dst>()
|
|
where
|
|
Dst: TransmuteFrom<Src, { Assume::SAFETY }>
|
|
{}
|
|
}
|
|
|
|
fn validity() {
|
|
// An initialized byte is a valid uninitialized byte.
|
|
assert::is_maybe_transmutable::<u8, MaybeUninit<u8>>();
|
|
|
|
// An uninitialized byte is never a valid initialized byte.
|
|
assert::is_maybe_transmutable::<MaybeUninit<u8>, u8>(); //~ ERROR: cannot be safely transmuted
|
|
}
|
|
|
|
fn padding() {
|
|
#[repr(align(8))]
|
|
struct Align8;
|
|
|
|
#[repr(u8)]
|
|
enum ImplicitlyPadded {
|
|
A(Align8),
|
|
}
|
|
|
|
#[repr(u8)]
|
|
enum V0 {
|
|
V0 = 0,
|
|
}
|
|
|
|
#[repr(C)]
|
|
struct ExplicitlyPadded(V0, MaybeUninit<[u8; 7]>);
|
|
|
|
assert::is_maybe_transmutable::<ExplicitlyPadded, ImplicitlyPadded>();
|
|
assert::is_maybe_transmutable::<ImplicitlyPadded, ExplicitlyPadded>();
|
|
}
|