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.
21 lines
625 B
Plaintext
21 lines
625 B
Plaintext
error: macro expansion ignores `=>` and any tokens following
|
|
--> $DIR/macro-expand-to-match-arm.rs:3:18
|
|
|
|
|
LL | $pattern => $block
|
|
| ^^
|
|
...
|
|
LL | arm!(None => {}),
|
|
| ---------------- caused by the macro expansion here
|
|
|
|
|
= note: the usage of `arm!` is likely invalid in pattern context
|
|
= note: macros cannot expand to match arms
|
|
|
|
error: `match` arm with no body
|
|
--> $DIR/macro-expand-to-match-arm.rs:14:9
|
|
|
|
|
LL | arm!(None => {}),
|
|
| ^^^^^^^^^^^^^^^^- help: add a body after the pattern: `=> todo!(),`
|
|
|
|
error: aborting due to 2 previous errors
|
|
|