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
37 lines
1.0 KiB
Rust
37 lines
1.0 KiB
Rust
//! The target endianness should be a consideration in computing the layout of
|
|
//! an enum with a multi-byte tag.
|
|
|
|
#![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)
|
|
}>
|
|
{}
|
|
}
|
|
|
|
#[repr(u16)] enum Src { V = 0xCAFE }
|
|
|
|
#[repr(u8)] enum OxCA { V = 0xCA }
|
|
#[repr(u8)] enum OxFE { V = 0xFE }
|
|
|
|
#[cfg(target_endian = "big")] #[repr(C)] struct Expected(OxCA, OxFE);
|
|
#[cfg(target_endian = "big")] #[repr(C)] struct Unexpected(OxFE, OxCA);
|
|
|
|
#[cfg(target_endian = "little")] #[repr(C)] struct Expected(OxFE, OxCA);
|
|
#[cfg(target_endian = "little")] #[repr(C)] struct Unexpected(OxCA, OxFE);
|
|
|
|
fn should_respect_endianness() {
|
|
assert::is_transmutable::<Src, Expected>();
|
|
assert::is_transmutable::<Src, Unexpected>(); //~ ERROR cannot be safely transmuted
|
|
}
|