rust/tests/ui/consts/const-eval/const_raw_ptr_ops2.rs

fn main() {}

// fine
const Z: i32 = unsafe { *(&1 as *const i32) };

// bad, will thus error in miri
const Z2: i32 = unsafe { *(42 as *const i32) }; //~ ERROR dangling pointer
const Z3: i32 = unsafe { *(44 as *const i32) }; //~ ERROR dangling pointer
Remove the const_raw_ptr_comparison feature gate. We can never supply a meaningful implementation of this. Instead, the follow up commits will create two intrinsics that approximate comparisons: * `ptr_maybe_eq` * `ptr_maybe_ne` The fact that `ptr_maybe_eq(a, b)` is not necessarily the same value as `!ptr_maybe_ne(a, b)` is a symptom of this entire problem. 2020-06-12 19:25:14 +02:00			`fn main() {}`

remove const_raw_ptr_to_usize_cast feature 2021-07-10 11:33:42 +02:00			`// fine`
Remove the const_raw_ptr_comparison feature gate. We can never supply a meaningful implementation of this. Instead, the follow up commits will create two intrinsics that approximate comparisons: * `ptr_maybe_eq` * `ptr_maybe_ne` The fact that `ptr_maybe_eq(a, b)` is not necessarily the same value as `!ptr_maybe_ne(a, b)` is a symptom of this entire problem. 2020-06-12 19:25:14 +02:00			`const Z: i32 = unsafe { (&1 as const i32) };`
remove const_raw_ptr_to_usize_cast feature 2021-07-10 11:33:42 +02:00
			`// bad, will thus error in miri`
Use the informative error as the main const eval error message 2025-05-28 10:29:08 +00:00			`const Z2: i32 = unsafe { (42 as const i32) }; //~ ERROR dangling pointer`
			`const Z3: i32 = unsafe { (44 as const i32) }; //~ ERROR dangling pointer`