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.
23 lines
683 B
Plaintext
23 lines
683 B
Plaintext
error: macro expansion ignores expression `2` and any tokens following
|
|
--> $DIR/trait-non-item-macros.rs:3:9
|
|
|
|
|
LL | $a
|
|
| ^^
|
|
...
|
|
LL | bah!(2);
|
|
| ------- caused by the macro expansion here
|
|
|
|
|
= note: the usage of `bah!` is likely invalid in trait item context
|
|
|
|
error[E0308]: mismatched types
|
|
--> $DIR/trait-non-item-macros.rs:12:33
|
|
|
|
|
LL | let _recovery_witness: () = 0;
|
|
| -- ^ expected `()`, found integer
|
|
| |
|
|
| expected due to this
|
|
|
|
error: aborting due to 2 previous errors
|
|
|
|
For more information about this error, try `rustc --explain E0308`.
|