mirror of
https://github.com/rust-lang/rust.git
synced 2024-11-23 15:23:46 +00:00
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
27 lines
595 B
Rust
27 lines
595 B
Rust
#![crate_type = "lib"]
|
|
#![feature(transmutability)]
|
|
mod assert {
|
|
use std::mem::TransmuteFrom;
|
|
|
|
pub fn is_maybe_transmutable<Src, Dst>()
|
|
where
|
|
Dst: TransmuteFrom<Src>,
|
|
{
|
|
}
|
|
}
|
|
|
|
fn main() {
|
|
pub union Uninit {
|
|
a: [u8; usize::MAX],
|
|
}
|
|
|
|
#[repr(C)]
|
|
struct ExplicitlyPadded(Uninit);
|
|
|
|
assert::is_maybe_transmutable::<(), ExplicitlyPadded>();
|
|
//~^ ERROR `()` cannot be safely transmuted into `ExplicitlyPadded`
|
|
|
|
assert::is_maybe_transmutable::<ExplicitlyPadded, ()>();
|
|
//~^ ERROR `ExplicitlyPadded` cannot be safely transmuted into `()`
|
|
}
|