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.
33 lines
1.0 KiB
Plaintext
33 lines
1.0 KiB
Plaintext
error: expected expression, found end of macro arguments
|
|
--> $DIR/attr-invalid-exprs.rs:12:13
|
|
|
|
|
LL | let _ = #[no_output] "Hello, world!";
|
|
| ^^^^^^^^^^^^
|
|
|
|
error: macro expansion ignores `,` and any tokens following
|
|
--> $DIR/attr-invalid-exprs.rs:15:13
|
|
|
|
|
LL | let _ = #[duplicate] "Hello, world!";
|
|
| ^^^^^^^^^^^^ caused by the macro expansion here
|
|
|
|
|
= note: the usage of `duplicate!` is likely invalid in expression context
|
|
help: you might be missing a semicolon here
|
|
|
|
|
LL | let _ = #[duplicate]; "Hello, world!";
|
|
| +
|
|
|
|
error: macro expansion ignores `,` and any tokens following
|
|
--> $DIR/attr-invalid-exprs.rs:24:9
|
|
|
|
|
LL | #[duplicate]
|
|
| ^^^^^^^^^^^^ caused by the macro expansion here
|
|
|
|
|
= note: the usage of `duplicate!` is likely invalid in expression context
|
|
help: you might be missing a semicolon here
|
|
|
|
|
LL | #[duplicate];
|
|
| +
|
|
|
|
error: aborting due to 3 previous errors
|
|
|