os-rust/tests/ui/unsafe/unsafe-const-fn.stderr

error[E0133]: call to unsafe function `dummy` is unsafe and requires unsafe function or block
  --> $DIR/unsafe-const-fn.rs:7:18
   |
LL | const VAL: u32 = dummy(0xFFFF);
   |                  ^^^^^^^^^^^^^ call to unsafe function
   |
   = note: consult the function's documentation for information on how to avoid undefined behavior

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0133`.
Stabilize THIR unsafeck 2023-12-07 11:56:48 +00:00			error[E0133]: call to unsafe function `dummy` is unsafe and requires unsafe function or block
Remove revisions for THIR unsafeck This is to make the diff when stabilizing it easier to review. 2023-10-26 16:13:20 +00:00			`--> $DIR/unsafe-const-fn.rs:7:18`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 22:47:55 +03:00			`\|`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| const VAL: u32 = dummy(0xFFFF);`
only show a simple description in E0133 span label 2022-04-24 14:42:30 +02:00			`\| ^^^^^^^^^^^^^ call to unsafe function`
improve error message shown for unsafe operations: explain why undefined behavior could arise Inspired by @gnzlbg at https://github.com/rust-lang/rust/issues/46043#issuecomment-381544673 2018-07-10 10:52:05 +02:00			`\|`
			`= note: consult the function's documentation for information on how to avoid undefined behavior`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 22:47:55 +03: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`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 22:47:55 +03:00
update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0133`.