Commits on Nov 2, 2020

1. Treat trailing semicolon as a statement in macro call …

   See rust-lang#61733 (comment)
   
   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.

   

   Aaron1011 committed Nov 2, 2020
   Configuration menu

   • View commit details
   • Copy full SHA for e78e9d4
   • Browse repository at this point

   Copy the full SHA

   e78e9d4 View commit details

   Browse the repository at this point in the history