os-rust/tests/ui/codemap_tests/issue-28308.stderr

error[E0600]: cannot apply unary operator `!` to type `&'static str`
  --> $DIR/issue-28308.rs:2:5
   |
LL |     assert!("foo");
   |     ^^^^^^^^^^^^^^ cannot apply unary operator `!`
   |
   = note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0600`.
Add invalid unary operator usage error code 2017-05-27 21:34:59 +02:00			error[E0600]: cannot apply unary operator `!` to type `&'static str`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-28308.rs:2:5`
Replace local backtrace with def-use, repair std macro spans 2016-08-17 07:20:04 -07:00			`\|`
Update UI tests 2018-02-23 03:42:32 +03:00			`LL \| assert!("foo");`
Bless tests 2021-10-14 13:28:28 -05:00			\| ^^^^^^^^^^^^^^ cannot apply unary operator `!`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 15:56:47 +02:00			`\|`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 14:52:25 -05:00			= note: this error originates in the macro `assert` (in Nightly builds, run with -Z macro-backtrace for more info)
Replace local backtrace with def-use, repair std macro spans 2016-08-17 07:20:04 -07: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`
Replace local backtrace with def-use, repair std macro spans 2016-08-17 07:20:04 -07:00
update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0600`.