rust/tests/ui/transmutability/references/accept_unexercised_lifetime_extension.rs
Jack Wrenn 1ad218f3af safe transmute: Rename BikeshedIntrinsicFrom to TransmuteFrom
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
2024-08-27 14:05:54 +00:00

69 lines
1.2 KiB
Rust

//@ check-pass
//! Accept lifetime extensions of un-exercised lifetimes.
#![feature(transmutability, core_intrinsics)]
use std::mem::{Assume, TransmuteFrom};
unsafe fn transmute<Src, Dst>(src: Src) -> Dst
where
Dst: TransmuteFrom<Src, { Assume::SAFETY }>,
{
core::intrinsics::transmute_unchecked(src)
}
enum Void {}
mod phantom {
use super::*;
use std::marker::PhantomData;
fn extend_bare<'a>(src: PhantomData<&'a u8>) -> PhantomData<&'static u8> {
unsafe { transmute(src) }
}
}
mod tuple {
use super::*;
fn extend_pair<'a>(src: (&'a u8, Void)) -> (&'static u8, Void) {
unsafe { transmute(src) }
}
}
mod r#struct {
use super::*;
struct Struct<'a>(&'a u8, Void);
fn extend_struct<'a>(src: Struct<'a>) -> Struct<'static> {
unsafe { transmute(src) }
}
}
mod r#enum {
use super::*;
enum Single<'a> {
A(&'a u8, Void),
}
fn extend_single<'a>(src: Single<'a>) -> Single<'static> {
unsafe { transmute(src) }
}
enum Multi<'a> {
A(&'a u8, Void),
B,
C,
}
fn extend_multi<'a>(src: Multi<'a>) -> Multi<'static> {
unsafe { transmute(src) }
}
}
fn main() {}