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.
14 lines
325 B
Plaintext
14 lines
325 B
Plaintext
error: macro expansion ignores keyword `let` and any tokens following
|
|
--> $DIR/issue-54441.rs:3:9
|
|
|
|
|
LL | let
|
|
| ^^^
|
|
...
|
|
LL | m!();
|
|
| ---- caused by the macro expansion here
|
|
|
|
|
= note: the usage of `m!` is likely invalid in foreign item context
|
|
|
|
error: aborting due to 1 previous error
|
|
|