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
38 lines
1010 B
Rust
38 lines
1010 B
Rust
//@ check-fail
|
|
#![feature(generic_const_exprs, transmutability)]
|
|
#![allow(incomplete_features)]
|
|
|
|
mod assert {
|
|
use std::mem::{Assume, TransmuteFrom};
|
|
|
|
pub fn is_transmutable<
|
|
Src,
|
|
Dst,
|
|
const ASSUME_ALIGNMENT: bool,
|
|
const ASSUME_LIFETIMES: bool,
|
|
const ASSUME_SAFETY: bool,
|
|
const ASSUME_VALIDITY: bool,
|
|
>()
|
|
where
|
|
Dst: TransmuteFrom<
|
|
Src,
|
|
{ from_options(ASSUME_ALIGNMENT, ASSUME_LIFETIMES, ASSUME_SAFETY, ASSUME_VALIDITY) }
|
|
>,
|
|
{}
|
|
|
|
// This should not cause an ICE
|
|
const fn from_options(
|
|
, //~ ERROR expected parameter name, found `,`
|
|
, //~ ERROR expected parameter name, found `,`
|
|
, //~ ERROR expected parameter name, found `,`
|
|
, //~ ERROR expected parameter name, found `,`
|
|
) -> Assume {} //~ ERROR mismatched types
|
|
}
|
|
|
|
fn main() {
|
|
#[repr(C)] struct Src;
|
|
#[repr(C)] struct Dst;
|
|
|
|
assert::is_transmutable::<Src, Dst, false, false, { true }, false>();
|
|
}
|