-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Macro with empty expansion in expression position causes an "unexpected <eof>" error #10951
Comments
Still happening as of latest nightly:
|
This is still happening
|
Still happening. |
@jseyfried just pinging you to make you aware and spark your interest. |
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 |
Macro diagnostics tweaks Fix rust-lang#30128, fix rust-lang#10951 by adding an appropriate span to the diagnostic. Fix rust-lang#26288 by suggesting adding semicolon to macro call.
Macro diagnostics tweaks Fix rust-lang#30128, fix rust-lang#10951 by adding an appropriate span to the diagnostic. Fix rust-lang#26288 by suggesting adding semicolon to macro call.
new lint [`single_call_fn`] Closes rust-lang#10861 changelog: New lint [`single_call_fn`]
(Moving the
foo!()
outsidemain
works.)The text was updated successfully, but these errors were encountered: