Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upMacro with empty expansion in expression position causes an "unexpected <eof>" error #10951
Comments
This comment has been minimized.
This comment has been minimized.
|
Still happening as of latest nightly:
|
This comment has been minimized.
This comment has been minimized.
charlesetc
commented
Nov 2, 2015
|
This is still happening
|
makoConstruct
referenced this issue
Jan 18, 2016
Closed
macro expanding to nothing in match arm causes uninformative parse error #30128
This comment has been minimized.
This comment has been minimized.
|
Still happening. |
brson
added
A-macros
P-low
I-wrong
labels
Apr 11, 2017
This comment has been minimized.
This comment has been minimized.
|
@jseyfried just pinging you to make you aware and spark your interest. |
This comment has been minimized.
This comment has been minimized.
|
The issue here is that This distinction isn't ideal, but I've already cleaned it up about as much as possible given back-compat constraints (see #34660), so I'm not sure there's much we can do about it now. cc @nrc |
Mark-Simulacrum
added
C-enhancement
and removed
C-enhancement
I-wrong
labels
Jul 20, 2017
kennytm
added a commit
to kennytm/rust
that referenced
this issue
Oct 26, 2018
kennytm
added a commit
to kennytm/rust
that referenced
this issue
Oct 26, 2018
kennytm
added a commit
to kennytm/rust
that referenced
this issue
Oct 26, 2018
bors
closed this
in
#55292
Oct 26, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
huonw commentedDec 13, 2013
(Moving the
foo!()outsidemainworks.)