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
35 lines
855 B
Rust
35 lines
855 B
Rust
//! Validity must be satisfiable, even if validity is assumed.
|
|
|
|
#![crate_type = "lib"]
|
|
#![feature(transmutability)]
|
|
#![allow(dead_code, incomplete_features, non_camel_case_types)]
|
|
|
|
mod assert {
|
|
use std::mem::{Assume, TransmuteFrom};
|
|
|
|
pub fn is_maybe_transmutable<Src, Dst>()
|
|
where
|
|
Dst: TransmuteFrom<Src, { Assume::SAFETY.and(Assume::VALIDITY) }>
|
|
{}
|
|
}
|
|
|
|
#[derive(Clone, Copy)] #[repr(u8)] enum Ox00 { V = 0x00 }
|
|
#[derive(Clone, Copy)] #[repr(u8)] enum Ox01 { V = 0x01 }
|
|
#[derive(Clone, Copy)] #[repr(u8)] enum OxFF { V = 0xFF }
|
|
|
|
fn test() {
|
|
#[repr(C)]
|
|
union A {
|
|
a: Ox00,
|
|
b: OxFF,
|
|
}
|
|
|
|
#[repr(C)]
|
|
union B {
|
|
c: Ox01,
|
|
}
|
|
|
|
assert::is_maybe_transmutable::<A, B>(); //~ ERROR cannot be safely transmuted
|
|
assert::is_maybe_transmutable::<B, A>(); //~ ERROR cannot be safely transmuted
|
|
}
|