rust/src/test/ui/macros/macro-backtrace-nested.stderr

error[E0425]: cannot find value `fake` in this scope
  --> $DIR/macro-backtrace-nested.rs:5:12
   |
LL |     () => (fake)
   |            ^^^^ not found in this scope
...
LL |     1 + call_nested_expr!();
   |         ------------------- in this macro invocation
   |
   = note: this error originates in the macro `nested_expr` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0425]: cannot find value `fake` in this scope
  --> $DIR/macro-backtrace-nested.rs:5:12
   |
LL |     () => (fake)
   |            ^^^^ not found in this scope
...
LL |     call_nested_expr_sum!();
   |     ----------------------- in this macro invocation
   |
   = note: this error originates in the macro `nested_expr` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0425`.
resolve: Do not use "resolve"/"resolution" in error messages 2017-01-11 16:18:08 -06:00			error[E0425]: cannot find value `fake` in this scope
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/macro-backtrace-nested.rs:5:12`
Replace local backtrace with def-use, repair std macro spans 2016-08-17 09:20:04 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| () => (fake)`
resolve: Do not use "resolve"/"resolution" in error messages 2017-01-11 16:18:08 -06:00			`\| ^^^^ not found in this scope`
Replace local backtrace with def-use, repair std macro spans 2016-08-17 09:20:04 -05:00			`...`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| 1 + call_nested_expr!();`
Replace local backtrace with def-use, repair std macro spans 2016-08-17 09:20:04 -05:00			`\| ------------------- in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 07:56:47 -06: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 13:52:25 -06:00			= note: this error originates in the macro `nested_expr` (in Nightly builds, run with -Z macro-backtrace for more info)
Replace local backtrace with def-use, repair std macro spans 2016-08-17 09:20:04 -05:00
resolve: Do not use "resolve"/"resolution" in error messages 2017-01-11 16:18:08 -06:00			error[E0425]: cannot find value `fake` in this scope
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/macro-backtrace-nested.rs:5:12`
Replace local backtrace with def-use, repair std macro spans 2016-08-17 09:20:04 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| () => (fake)`
resolve: Do not use "resolve"/"resolution" in error messages 2017-01-11 16:18:08 -06:00			`\| ^^^^ not found in this scope`
Replace local backtrace with def-use, repair std macro spans 2016-08-17 09:20:04 -05:00			`...`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| call_nested_expr_sum!();`
Bless tests 2021-10-14 13:28:28 -05:00			`\| ----------------------- in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 07:56:47 -06: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 13:52:25 -06:00			= note: this error originates in the macro `nested_expr` (in Nightly builds, run with -Z macro-backtrace for more info)
Replace local backtrace with def-use, repair std macro spans 2016-08-17 09:20:04 -05:00
Revert "Change error count messages" This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e. 2017-07-02 05:49:30 -05:00			`error: aborting due to 2 previous errors`
Replace local backtrace with def-use, repair std macro spans 2016-08-17 09:20:04 -05:00
update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0425`.