rust/tests/ui/unsafe/unsafe-fn-called-from-safe.thir.stderr

error[E0133]: call to unsafe function `f` is unsafe and requires unsafe function or block
  --> $DIR/unsafe-fn-called-from-safe.rs:7:5
   |
LL |     f();
   |     ^^^ 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 07:08:23 -05:00			error[E0133]: call to unsafe function `f` is unsafe and requires unsafe function or block
Test `-Zthir-unsafeck` for unsafe function calls 2021-03-14 14:11:37 -05:00			`--> $DIR/unsafe-fn-called-from-safe.rs:7:5`
Move some E0XXX to `ui` 2018-02-07 21:35:35 -06:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| f();`
only show a simple description in E0133 span label 2022-04-24 07:42:30 -05: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 03:52:05 -05:00			`\|`
			`= note: consult the function's documentation for information on how to avoid undefined behavior`
Move some E0XXX to `ui` 2018-02-07 21:35:35 -06:00
			`error: aborting due to previous error`

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