rust/src/test/ui/consts/const-eval/const_raw_ptr_ops2.rs

#![feature(const_raw_ptr_deref)]

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 any use of this value will cause
//~| WARN this was previously accepted by the compiler but is being phased out
const Z3: i32 = unsafe { *(44 as *const i32) }; //~ ERROR any use of this value will cause
//~| WARN this was previously accepted by the compiler but is being phased out
remove const_raw_ptr_to_usize_cast feature 2021-07-10 04:33:42 -05:00			`#![feature(const_raw_ptr_deref)]`
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 12:25:14 -05:00
			`fn main() {}`

remove const_raw_ptr_to_usize_cast feature 2021-07-10 04:33:42 -05: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 12:25:14 -05:00			`const Z: i32 = unsafe { (&1 as const i32) };`
remove const_raw_ptr_to_usize_cast feature 2021-07-10 04:33:42 -05:00
			`// bad, will thus error in miri`
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 12:25:14 -05:00			`const Z2: i32 = unsafe { (42 as const i32) }; //~ ERROR any use of this value will cause`
make const_err a future incompat lint 2021-01-30 07:49:22 -06:00			`//~\| WARN this was previously accepted by the compiler but is being phased out`
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 12:25:14 -05:00			`const Z3: i32 = unsafe { (44 as const i32) }; //~ ERROR any use of this value will cause`
make const_err a future incompat lint 2021-01-30 07:49:22 -06:00			`//~\| WARN this was previously accepted by the compiler but is being phased out`