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
33 lines
593 B
Rust
33 lines
593 B
Rust
//@ check-pass
|
|
//! Tests that we do not regress rust-lang/rust#125811
|
|
#![feature(transmutability)]
|
|
|
|
fn assert_transmutable<T>()
|
|
where
|
|
(): std::mem::TransmuteFrom<T>
|
|
{}
|
|
|
|
enum Uninhabited {}
|
|
|
|
enum SingleInhabited {
|
|
X,
|
|
Y(Uninhabited)
|
|
}
|
|
|
|
enum SingleUninhabited {
|
|
X(Uninhabited),
|
|
Y(Uninhabited),
|
|
}
|
|
|
|
enum MultipleUninhabited {
|
|
X(u8, Uninhabited),
|
|
Y(Uninhabited, u16),
|
|
}
|
|
|
|
fn main() {
|
|
assert_transmutable::<Uninhabited>();
|
|
assert_transmutable::<SingleInhabited>();
|
|
assert_transmutable::<SingleUninhabited>();
|
|
assert_transmutable::<MultipleUninhabited>();
|
|
}
|