rust/tests/ui/issues/issue-28776.thir.stderr

error[E0133]: call to unsafe function `std::ptr::write` is unsafe and requires unsafe function or block
  --> $DIR/issue-28776.rs:7:5
   |
LL |     (&ptr::write)(1 as *mut _, 42);
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function
   |
   = note: consult the function's documentation for information on how to avoid undefined behavior

error: aborting due to previous error

For more information about this error, try `rustc --explain E0133`.
add `DefId` to unsafety violations and display function path in E0133 this enables consumers to access the function definition that was reported to be unsafe 2022-04-24 14:08:23 +02:00			error[E0133]: call to unsafe function `std::ptr::write` is unsafe and requires unsafe function or block
Test `-Zthir-unsafeck` for unsafe function calls 2021-03-14 20:11:37 +01:00			`--> $DIR/issue-28776.rs:7:5`
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 \| (&ptr::write)(1 as *mut _, 42);`
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
			`error: aborting due to previous error`

update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0133`.