Forgot one, of course: =

@cmr, was there a reason for not including Semicolon on this list as well?
It's handy when defining matchers like $( fn $n:ident( $(p:ident : $t:ty),* ) -> $r:ty ; )* (note the trailing 'ty')

No, that was indeed an oversight

sent from my phone
On Jan 23, 2015 12:24 AM, "Vadim Chugunov" notifications@github.com wrote:

In text/0000-macro-future-proofing.md
#550 (comment):

•   continue, else, reject.
  

• 2. If T has the form $(...)U+ or $(...)U* for some token U, run

•   the algorithm on the contents with `F` set to `U`. If it accepts,
  

•   check that the last token in the sequence can be followed by `F`. If
  

•   so, accept. Otherwise, reject.
  

  +This algorithm should be run on every matcher in every macro_rules
  +invocation, with F as EOF. If it rejects a matcher, an error should be
  +emitted and compilation should not complete.
  +
  +The current legal fragment specifiers are: item, block, stmt, pat,
  +expr, ty, ident, path, meta, and tt.
  +
  +- FOLLOW(pat) = {FatArrow, Comma, Eq}
  +- FOLLOW(expr) = {FatArrow, Comma, Semicolon}
  +- FOLLOW(ty) = {Comma, FatArrow, Colon, Eq, Gt, Ident(as)}

@cmr https://github.com/cmr, was there a reason for not including
Semicolon on this list as well?
It's handy when defining matchers like $( fn $n:ident( $(p:ident :
$t:ty),* ) -> $r:ty ; )* (note the trailing 'ty')

—
Reply to this email directly or view it on GitHub
https://github.com/rust-lang/rfcs/pull/550/files#r23432570.