os-rust/tests/ui/proc-macro/lints_in_proc_macros.stderr

error[E0425]: cannot find value `foobar2` in this scope
  --> $DIR/lints_in_proc_macros.rs:9:5
   |
LL |     bang_proc_macro2!();
   |     ^^^^^^^^^^^^^^^^^^^ help: a local variable with a similar name exists: `foobar`
   |
   = note: this error originates in the macro `bang_proc_macro2` (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 E0425`.
Move former compile-fail-fulldeps tests to ui 2018-12-02 22:27:37 +03:00			error[E0425]: cannot find value `foobar2` in this scope
Stabilize fn-like proc macros in expression, pattern and statement positions 2020-02-01 01:02:31 +03:00			`--> $DIR/lints_in_proc_macros.rs:9:5`
Move former compile-fail-fulldeps tests to ui 2018-12-02 22:27:37 +03:00			`\|`
			`LL \| bang_proc_macro2!();`
Bless tests 2021-10-14 13:28:28 -05:00			\| ^^^^^^^^^^^^^^^^^^^ help: a local variable with a similar name exists: `foobar`
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 `bang_proc_macro2` (in Nightly builds, run with -Z macro-backtrace for more info)
Move former compile-fail-fulldeps tests to ui 2018-12-02 22:27:37 +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 former compile-fail-fulldeps tests to ui 2018-12-02 22:27:37 +03:00
			For more information about this error, try `rustc --explain E0425`.