-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
'expected identifier' when 'as' keyword appears after block #17930
Labels
A-grammar
Area: The grammar of Rust
C-feature-request
Category: A feature request, i.e: not implemented / a PR.
Comments
I feel like this is a dup, but I can't find the issue. |
Updated code: fn main() {
unsafe { 0 as i32 }; // ok
unsafe { 0 } as i32; // expected identifier, found keyword `as`
(unsafe { 0 }) as i32; // ok
} same error. |
Triage: no change |
|
lnicola
pushed a commit
to lnicola/rust
that referenced
this issue
Aug 29, 2024
Remove the ability to configure the user config path Being able to do this makes little sense as this is effectively a cyclic dependency (and we do not want to fixpoint this really).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-grammar
Area: The grammar of Rust
C-feature-request
Category: A feature request, i.e: not implemented / a PR.
I'm not sure if this qualifies as bug but it's somewhat surprising to me:
The same happens with
match true { true => 0, false => 0 } as int
orif true { 0 } else { 0 } as int
unless the expression is wrapped in parentheses.The text was updated successfully, but these errors were encountered: