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
57 lines
1.1 KiB
Rust
57 lines
1.1 KiB
Rust
//@ check-pass
|
|
//! The implementation should behave correctly when the `ASSUME` parameters are
|
|
//! provided indirectly through an abstraction.
|
|
|
|
#![crate_type = "lib"]
|
|
#![feature(adt_const_params)]
|
|
#![feature(transmutability)]
|
|
#![allow(dead_code, incomplete_features, non_camel_case_types)]
|
|
|
|
mod assert {
|
|
use std::mem::TransmuteFrom;
|
|
|
|
pub fn is_transmutable<
|
|
Src,
|
|
Dst,
|
|
const ASSUME: std::mem::Assume,
|
|
>()
|
|
where
|
|
Dst: TransmuteFrom<
|
|
Src,
|
|
ASSUME,
|
|
>,
|
|
{}
|
|
}
|
|
|
|
fn direct() {
|
|
assert::is_transmutable::<(), (), { std::mem::Assume::NOTHING }>();
|
|
}
|
|
|
|
fn via_const() {
|
|
const FALSE: bool = false;
|
|
|
|
assert::is_transmutable::<(), (), { std::mem::Assume::NOTHING }>();
|
|
}
|
|
|
|
fn via_associated_const() {
|
|
trait Trait {
|
|
const FALSE: bool = true;
|
|
}
|
|
|
|
struct Ty;
|
|
|
|
impl Trait for Ty {}
|
|
|
|
assert::is_transmutable::<
|
|
(),
|
|
(),
|
|
{
|
|
std::mem::Assume {
|
|
alignment: {Ty::FALSE},
|
|
lifetimes: {Ty::FALSE},
|
|
safety: {Ty::FALSE},
|
|
validity: {Ty::FALSE},
|
|
}
|
|
}
|
|
>();
|
|
}
|