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.
28 lines
480 B
Rust
28 lines
480 B
Rust
macro_rules! ignored_item {
|
|
() => {
|
|
fn foo() {}
|
|
fn bar() {}
|
|
, //~ ERROR macro expansion ignores `,`
|
|
}
|
|
}
|
|
|
|
macro_rules! ignored_expr {
|
|
() => ( 1, //~ ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `,`
|
|
|
|
2 )
|
|
}
|
|
|
|
macro_rules! ignored_pat {
|
|
() => ( 1, 2 ) //~ ERROR macro expansion ignores `,`
|
|
}
|
|
|
|
ignored_item!();
|
|
|
|
fn main() {
|
|
ignored_expr!();
|
|
match 1 {
|
|
ignored_pat!() => (),
|
|
_ => (),
|
|
}
|
|
}
|