diff options
| author | Aaron Hill <aa1ronham@gmail.com> | 2020-10-25 17:14:19 -0400 |
|---|---|---|
| committer | Aaron Hill <aa1ronham@gmail.com> | 2020-11-02 13:03:13 -0500 |
| commit | e78e9d4a06192cfbb9e1417fdd7a0753d51684a3 (patch) | |
| tree | 50ad813cd0c21a4d99288be51fe7b837126a7748 /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp | |
| parent | 499ebcfdf3b09a646154f321b7c28f5105e4dbf7 (diff) | |
| download | rust-e78e9d4a06192cfbb9e1417fdd7a0753d51684a3.tar.gz rust-e78e9d4a06192cfbb9e1417fdd7a0753d51684a3.zip | |
Treat trailing semicolon as a statement in macro call
See https://github.com/rust-lang/rust/issues/61733#issuecomment-716188981
We now preserve the trailing semicolon in a macro invocation, even if
the macro expands to nothing. As a result, the following code no longer
compiles:
```rust
macro_rules! empty {
() => { }
}
fn foo() -> bool { //~ ERROR mismatched
{ true } //~ ERROR mismatched
empty!();
}
```
Previously, `{ true }` would be considered the trailing expression, even
though there's a semicolon in `empty!();`
This makes macro expansion more token-based.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
