rust/tests/ui/macros/issue-6596-1.stderr

error: expected expression, found `$`
  --> $DIR/issue-6596-1.rs:3:9
   |
LL |         $nonexistent
   |         ^^^^^^^^^^^^ expected expression
...
LL |     e!(foo);
   |     ------- in this macro invocation
   |
   = note: this error originates in the macro `e` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error
parser: Do not call `bump` recursively Token normalization is merged directly into `bump`. Special "unknown macro variable" diagnostic for unexpected `$`s is removed as preventing legal code from compiling. 2020-02-16 07:47:24 -06:00			error: expected expression, found `$`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-6596-1.rs:3:9`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`\|`
			`LL \| $nonexistent`
parser: Do not call `bump` recursively Token normalization is merged directly into `bump`. Special "unknown macro variable" diagnostic for unexpected `$`s is removed as preventing legal code from compiling. 2020-02-16 07:47:24 -06:00			`\| ^^^^^^^^^^^^ expected expression`
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00			`...`
			`LL \| e!(foo);`
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 `e` (in Nightly builds, run with -Z macro-backtrace for more info)
Move some `compile-fail` tests to `ui` 2018-07-15 16:11:54 -05:00
			`error: aborting due to previous error`