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.
18 lines
517 B
Rust
18 lines
517 B
Rust
//@ compile-flags: --crate-type lib -O -C debug-assertions=yes
|
|
|
|
// Regression test for issue 118786
|
|
|
|
macro_rules! make_macro {
|
|
($macro_name:tt) => {
|
|
macro_rules! $macro_name {
|
|
//~^ ERROR macro expansion ignores `{` and any tokens following
|
|
//~| ERROR cannot find macro `macro_rules` in this scope
|
|
//~| put a macro name here
|
|
() => {}
|
|
}
|
|
}
|
|
}
|
|
|
|
make_macro!((meow));
|
|
//~^ ERROR macros that expand to items must be delimited with braces or followed by a semicolon
|