rust/tests/ui/transmutability/structs/repr/should_handle_align.rs
Jack Wrenn 23ab1bda92 safe transmute: revise safety analysis
Migrate to a simplified safety analysis that does not use visibility.

Closes https://github.com/rust-lang/project-safe-transmute/issues/15
2024-02-27 16:22:32 +00:00

43 lines
1.2 KiB
Rust

//@ check-pass
//! The presence of an `align(X)` annotation must be accounted for.
#![crate_type = "lib"]
#![feature(transmutability)]
#![allow(dead_code, incomplete_features, non_camel_case_types)]
mod assert {
use std::mem::{Assume, BikeshedIntrinsicFrom};
pub fn is_maybe_transmutable<Src, Dst>()
where
Dst: BikeshedIntrinsicFrom<Src, {
Assume {
alignment: true,
lifetimes: true,
safety: true,
validity: true,
}
}>
{}
}
fn should_pad_explicitly_aligned_field() {
#[derive(Clone, Copy)] #[repr(u8)] enum V0u8 { V = 0 }
#[repr(C)]
pub union Uninit {
a: (),
b: V0u8,
}
#[repr(C, align(2))] struct align_2(V0u8);
#[repr(C)] struct ImplicitlyPadded(align_2, V0u8);
#[repr(C)] struct ExplicitlyPadded(V0u8, Uninit, V0u8);
// An implementation that (incorrectly) does not place a padding byte after
// `align_2` will, incorrectly, reject the following transmutations.
assert::is_maybe_transmutable::<ImplicitlyPadded, ExplicitlyPadded>();
assert::is_maybe_transmutable::<ExplicitlyPadded, ImplicitlyPadded>();
}