a201fab208
By using `token_descr`, as is done for many other errors, we can get slightly better descriptions in error messages, e.g. "macro expansion ignores token `let` and any following" becomes "macro expansion ignores keyword `let` and any tokens following". This will be more important once invisible delimiters start being mentioned in error messages -- without this commit, that leads to error messages such as "error at ``" because invisible delimiters are pretty printed as an empty string.
32 lines
1.3 KiB
Plaintext
32 lines
1.3 KiB
Plaintext
error: expected one of `(`, `,`, `=`, `{`, or `}`, found type `(String)`
|
|
--> $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 type `(String)` 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
|
|
|