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.
48 lines
1.4 KiB
Plaintext
48 lines
1.4 KiB
Plaintext
error: macros that expand to items must be delimited with braces or followed by a semicolon
|
|
--> $DIR/issue-118786.rs:16:13
|
|
|
|
|
LL | make_macro!((meow));
|
|
| ^^^^^^
|
|
|
|
|
help: change the delimiters to curly braces
|
|
|
|
|
LL | make_macro!({meow});
|
|
| ~ ~
|
|
help: add a semicolon
|
|
|
|
|
LL | macro_rules! $macro_name; {
|
|
| +
|
|
|
|
error: macro expansion ignores `{` and any tokens following
|
|
--> $DIR/issue-118786.rs:7:34
|
|
|
|
|
LL | macro_rules! $macro_name {
|
|
| ^
|
|
...
|
|
LL | make_macro!((meow));
|
|
| ------------------- caused by the macro expansion here
|
|
|
|
|
= note: the usage of `make_macro!` is likely invalid in item context
|
|
|
|
error: cannot find macro `macro_rules` in this scope
|
|
--> $DIR/issue-118786.rs:7:9
|
|
|
|
|
LL | macro_rules! $macro_name {
|
|
| ^^^^^^^^^^^
|
|
...
|
|
LL | make_macro!((meow));
|
|
| ------------------- in this macro invocation
|
|
|
|
|
note: maybe you have forgotten to define a name for this `macro_rules!`
|
|
--> $DIR/issue-118786.rs:7:20
|
|
|
|
|
LL | macro_rules! $macro_name {
|
|
| ^ put a macro name here
|
|
...
|
|
LL | make_macro!((meow));
|
|
| ------------------- in this macro invocation
|
|
= note: this error originates in the macro `make_macro` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: aborting due to 3 previous errors
|
|
|