rust/tests/ui/consts/const-eval/ub-enum-overwrite.stderr

error[E0080]: reading memory at ALLOC0[0x1..0x2], but memory is uninitialized at [0x1..0x2], and this operation requires initialized memory
  --> $DIR/ub-enum-overwrite.rs:11:14
   |
LL |     unsafe { *p }
   |              ^^ evaluation of `_` failed here
   |
   = note: the raw bytes of the constant (size: 2, align: 1) {
               01 __                                           │ .░
           }

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0080`.
Report the range of uninit bytes in CTFE errors 2025-06-18 12:51:47 +00:00			`error[E0080]: reading memory at ALLOC0[0x1..0x2], but memory is uninitialized at [0x1..0x2], and this operation requires initialized memory`
stabilize const_mut_refs 2024-08-17 14:19:34 +02:00			`--> $DIR/ub-enum-overwrite.rs:11:14`
Add const eval tests ensuring padding gets correctly marked as deinit on deaggregation 2022-04-05 19:12:09 -04:00			`\|`
make read_immediate error immediately on uninit, so ImmTy can carry initialized Scalar 2022-08-01 19:05:20 -04:00			`LL \| unsafe { *p }`
const-eval error: always say in which item the error occurred also adjust the wording a little so that we don't say "the error occurred here" for two different spans 2025-06-07 11:32:09 +02:00			\| ^^ evaluation of `_` failed here
Show the memory of uninit reads 2025-06-18 12:51:47 +00:00			`\|`
			`= note: the raw bytes of the constant (size: 2, align: 1) {`
			`01 __ │ .░`
			`}`
Add const eval tests ensuring padding gets correctly marked as deinit on deaggregation 2022-04-05 19:12:09 -04:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Add const eval tests ensuring padding gets correctly marked as deinit on deaggregation 2022-04-05 19:12:09 -04:00
			For more information about this error, try `rustc --explain E0080`.