rust/tests/ui/parser/macro/issue-37234.stderr

error: expected one of `.`, `;`, `?`, `else`, or an operator, found `""`
  --> $DIR/issue-37234.rs:3:19
   |
LL |         let x = 5 "";
   |                   ^^ expected one of `.`, `;`, `?`, `else`, or an operator
...
LL |     failed!();
   |     --------- in this macro invocation
   |
   = note: this error originates in the macro `failed` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 1 previous error
Fix tests 2021-08-01 19:55:48 -05:00			error: expected one of `.`, `;`, `?`, `else`, or an operator, found `""`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-37234.rs:3:19`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			`\|`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| let x = 5 "";`
Fix tests 2021-08-01 19:55:48 -05:00			\| ^^ expected one of `.`, `;`, `?`, `else`, or an operator
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			`...`
			`LL \| failed!();`
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 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 `failed` (in Nightly builds, run with -Z macro-backtrace for more info)
Move parse-fail tests to UI 2018-10-20 23:36:17 +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 parse-fail tests to UI 2018-10-20 23:36:17 +03:00