To be completely fair, the "macros 2.0" macro m() {} syntax is intended to be the proper syntax for declarative macros, eventually. However, that's blocked on proper "full" def site hygiene for them (rather than the "mixed site" hygiene that macro_rules! uses) along with a way to opt out of def site hygiene and get call site hygiene. Plus that syntax has never actually been RFCd (and the simple form doesn't even support multiple matching arms), so that's probably multiple years out, if we even ever get to "macros 2.0".
1 Like
Definitely, there are cases where it does not need the extra parenthesis at all.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.