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.
36 lines
1.1 KiB
Plaintext
36 lines
1.1 KiB
Plaintext
error: macro expansion ignores `,` and any tokens following
|
|
--> $DIR/macro-incomplete-parse.rs:5:9
|
|
|
|
|
LL | ,
|
|
| ^
|
|
...
|
|
LL | ignored_item!();
|
|
| --------------- caused by the macro expansion here
|
|
|
|
|
= note: the usage of `ignored_item!` is likely invalid in item context
|
|
|
|
error: expected one of `.`, `;`, `?`, `}`, or an operator, found `,`
|
|
--> $DIR/macro-incomplete-parse.rs:10:14
|
|
|
|
|
LL | () => ( 1,
|
|
| ^ expected one of `.`, `;`, `?`, `}`, or an operator
|
|
...
|
|
LL | ignored_expr!();
|
|
| --------------- in this macro invocation
|
|
|
|
|
= note: this error originates in the macro `ignored_expr` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: macro expansion ignores `,` and any tokens following
|
|
--> $DIR/macro-incomplete-parse.rs:16:14
|
|
|
|
|
LL | () => ( 1, 2 )
|
|
| ^
|
|
...
|
|
LL | ignored_pat!() => (),
|
|
| -------------- caused by the macro expansion here
|
|
|
|
|
= note: the usage of `ignored_pat!` is likely invalid in pattern context
|
|
|
|
error: aborting due to 3 previous errors
|
|
|