| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2016-10-18 | Fix some pretty printing tests | Vadim Petrochenkov | -2/+0 | |
| 2015-01-05 | Un-gate macro_rules | Keegan McAllister | -2/+0 | |
| 2015-01-05 | Modernize macro_rules! invocations | Keegan McAllister | -2/+2 | |
| macro_rules! is like an item that defines a macro. Other items don't have a trailing semicolon, or use a paren-delimited body. If there's an argument for matching the invocation syntax, e.g. parentheses for an expr macro, then I think that applies more strongly to the *inner* delimiters on the LHS, wrapping the individual argument patterns. | ||||
| 2014-12-18 | librustc: Always parse `macro!()`/`macro![]` as expressions if not | Patrick Walton | -2/+2 | |
| followed by a semicolon. This allows code like `vec![1i, 2, 3].len();` to work. This breaks code that uses macros as statements without putting semicolons after them, such as: fn main() { ... assert!(a == b) assert!(c == d) println(...); } It also breaks code that uses macros as items without semicolons: local_data_key!(foo) fn main() { println("hello world") } Add semicolons to fix this code. Those two examples can be fixed as follows: fn main() { ... assert!(a == b); assert!(c == d); println(...); } local_data_key!(foo); fn main() { println("hello world") } RFC #378. Closes #18635. [breaking-change] | ||||
| 2014-04-14 | Use new attribute syntax in python files in src/etc too (#13478) | Manish Goregaokar | -1/+1 | |
| 2014-02-11 | Change `xfail` directives in compiletests to `ignore`, closes #11363 | Florian Hahn | -2/+2 | |
| 2013-11-26 | Support multiple item macros | Steven Fackler | -0/+29 | |
| Closes #4375 | ||||
