
Notes about tests: - tests/ui/parser/macro/trait-object-macro-matcher.rs: the syntax error is duplicated, because it occurs now when parsing the decl macro input, and also when parsing the expanded decl macro. But this won't show up for normal users due to error de-duplication. - tests/ui/associated-consts/issue-93835.rs: similar, plus there are some additional errors about this very broken code. - The changes to metavariable descriptions in #132629 are now visible in error message for several tests.
31 lines
1.3 KiB
Text
31 lines
1.3 KiB
Text
error: expected one of `(`, `,`, `=`, `{`, or `}`, found `ty` metavariable
|
|
--> $DIR/syntax-error-recovery.rs:7:26
|
|
|
|
|
LL | $token $($inner)? = $value,
|
|
| ^^^^^^ expected one of `(`, `,`, `=`, `{`, or `}`
|
|
...
|
|
LL | values!(STRING(1) as (String) => cfg(test),);
|
|
| -------------------------------------------- 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 `values` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: macro expansion ignores `ty` metavariable and any tokens following
|
|
--> $DIR/syntax-error-recovery.rs:7:26
|
|
|
|
|
LL | $token $($inner)? = $value,
|
|
| ^^^^^^
|
|
...
|
|
LL | values!(STRING(1) as (String) => cfg(test),);
|
|
| -------------------------------------------- caused by the macro expansion here
|
|
|
|
|
= note: the usage of `values!` is likely invalid in item context
|
|
|
|
error: expected one of `!` or `::`, found `<eof>`
|
|
--> $DIR/syntax-error-recovery.rs:15:9
|
|
|
|
|
LL | values!(STRING(1) as (String) => cfg(test),);
|
|
| ^^^^^^ expected one of `!` or `::`
|
|
|
|
error: aborting due to 3 previous errors
|
|
|