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
56 lines
1.1 KiB
Rust
56 lines
1.1 KiB
Rust
//@ check-pass
|
|
|
|
#![crate_type = "lib"]
|
|
#![feature(transmutability, transparent_unions)]
|
|
#![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 {
|
|
alignment: true,
|
|
lifetimes: true,
|
|
safety: true,
|
|
validity: true,
|
|
}
|
|
}>
|
|
{}
|
|
}
|
|
|
|
fn should_accept_repr_rust()
|
|
{
|
|
union repr_rust {
|
|
a: u8
|
|
}
|
|
|
|
assert::is_maybe_transmutable::<repr_rust, ()>();
|
|
assert::is_maybe_transmutable::<u128, repr_rust>();
|
|
}
|
|
|
|
fn should_accept_repr_c()
|
|
{
|
|
#[repr(C)]
|
|
union repr_c {
|
|
a: u8
|
|
}
|
|
|
|
struct repr_rust;
|
|
assert::is_maybe_transmutable::<repr_c, ()>();
|
|
assert::is_maybe_transmutable::<u128, repr_c>();
|
|
}
|
|
|
|
|
|
fn should_accept_transparent()
|
|
{
|
|
#[repr(transparent)]
|
|
union repr_transparent {
|
|
a: u8
|
|
}
|
|
|
|
assert::is_maybe_transmutable::<repr_transparent, ()>();
|
|
assert::is_maybe_transmutable::<u128, repr_transparent>();
|
|
}
|