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
781 B
Rust
27 lines
781 B
Rust
// An unknown destination type should be gracefully handled.
|
|
|
|
#![crate_type = "lib"]
|
|
#![feature(transmutability)]
|
|
#![allow(dead_code, incomplete_features, non_camel_case_types)]
|
|
|
|
mod assert {
|
|
use std::mem::TransmuteFrom;
|
|
|
|
pub fn is_transmutable<Src, Dst>()
|
|
where
|
|
Dst: TransmuteFrom<Src>
|
|
{}
|
|
}
|
|
|
|
fn should_gracefully_handle_unknown_src_field() {
|
|
#[repr(C)] struct Src(Missing); //~ cannot find type
|
|
#[repr(C)] struct Dst();
|
|
assert::is_transmutable::<Src, Dst>(); //~ ERROR cannot be safely transmuted
|
|
}
|
|
|
|
fn should_gracefully_handle_unknown_src_ref_field() {
|
|
#[repr(C)] struct Src(&'static Missing); //~ cannot find type
|
|
#[repr(C)] struct Dst(&'static Dst);
|
|
assert::is_transmutable::<Src, Dst>(); //~ ERROR cannot be safely transmuted
|
|
}
|