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

error: expected identifier, found `String`
  --> $DIR/issue-37113.rs:4:16
   |
LL |         enum SomeEnum {
   |              -------- while parsing this enum
LL |             $( $t, )*
   |                ^^ expected identifier
...
LL |     test_macro!(String,);
   |     -------------------- in this macro invocation
   |
   = help: enum variants can be `Variant`, `Variant = <integer>`, `Variant(Type, ..., TypeN)` or `Variant { fields: Types }`
   = note: this error originates in the macro `test_macro` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			error: expected identifier, found `String`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/issue-37113.rs:4:16`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			`\|`
add a label to struct/enum/union ident name 2022-09-26 23:13:38 +09:00			`LL \| enum SomeEnum {`
			`\| -------- while parsing this enum`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| $( $t, )*`
Move parse-fail tests to UI 2018-10-20 23:36:17 +03:00			`\| ^^ expected identifier`
			`...`
			`LL \| test_macro!(String,);`
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			`\|`
While parsing enum variant, the error message always disappear Because the error message that emit out is from main error of parser The information of enum variant disappears while parsing enum variant with error We only check the syntax of expecting token, i.e, in case #103869 It will error it without telling the message that this error is from pasring enum variant. Propagate the sub-error from parsing enum variant to the main error of parser by chaining it with map_err Check the sub-error before emitting the main error of parser and attach it. Fix #103869 2022-11-30 12:01:00 -08:00			= help: enum variants can be `Variant`, `Variant = <integer>`, `Variant(Type, ..., TypeN)` or `Variant { fields: Types }`
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 `test_macro` (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
			`error: aborting due to previous error`