-
Notifications
You must be signed in to change notification settings - Fork 13k
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
issues with stmt arguments to macros #13679
Comments
Duplicate of #3232. The local ambiguity is caused by two states corresponding to |
Closing as a dupe (as noted by @lifthrasiir) |
arcnmx
pushed a commit
to arcnmx/rust
that referenced
this issue
Dec 17, 2022
feat: allow unwrap block in let initializers Possible fix for rust-lang#13679 ### Points to help in review: - I just added a parent case for let statements and it seems everything else was in place already, so turned out to be a small fix
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Nov 28, 2024
…3695) Close rust-lang#13679 changelog: [`if_let_mutex`]: disable lint from Edition 2024 since [stabilized if_let_rescope ](rust-lang#131154)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not exactly sure what it's supposed to do, but it seems wrong:
As is, we get:
even though there is no way
}
could start a statement. With thelet
instead, it'swhich doesn't seem to make sense either.
rustc 0.11-pre-nightly (d35804e 2014-04-18 00:01:22 -0700)
The text was updated successfully, but these errors were encountered: