Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Mention expectation of { for parse error immediately after async in expressions #80931

Open
estebank opened this issue Jan 12, 2021 · 0 comments
Open

Mention expectation of { for parse error immediately after async in expressions #80931

estebank opened this issue Jan 12, 2021 · 0 comments
Labels
A-diagnostics Area: Messages for errors, warnings, and lints A-parser Area: The parsing of Rust source code to an AST C-enhancement Category: An issue proposing an enhancement or a PR with one. D-papercut Diagnostics: An error or lint that needs small tweaks. P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@estebank
Copy link
Contributor

The following code

rust/src/test/ui/parser/block-no-opening-brace.stderr

Lines 34 to 40 in fe531d5

error: expected one of `move`, `|`, or `||`, found keyword `let`
--> $DIR/block-no-opening-brace.rs:30:9
|
LL | async
| - expected one of `move`, `|`, or `||`
LL | let x = 0;
| ^^^ unexpected token

should also mention an expectation for an open brace {, and potentially even suggesting a new block, like the other test cases in that file.
@estebank estebank added A-diagnostics Area: Messages for errors, warnings, and lints A-parser Area: The parsing of Rust source code to an AST P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. D-papercut Diagnostics: An error or lint that needs small tweaks. labels Jan 12, 2021
@estebank estebank mentioned this issue Jan 12, 2021
Merged
@JohnTitor JohnTitor added the C-enhancement Category: An issue proposing an enhancement or a PR with one. label Jan 12, 2021
@GrigorenkoPV GrigorenkoPV mentioned this issue Sep 22, 2024
Merged
workingjubilee added a commit to workingjubilee/rustc that referenced this issue Sep 23, 2024
@workingjubilee
Rollup merge of rust-lang#130721 - GrigorenkoPV:block-no-opening-brac…
acb25ca 
…e, r=jieyouxu

Add more test cases for block-no-opening-brace

Also add FIXME's for rust-lang#80931 & rust-lang#78168
workingjubilee added a commit to workingjubilee/rustc that referenced this issue Sep 23, 2024
@workingjubilee
Rollup merge of rust-lang#130721 - GrigorenkoPV:block-no-opening-brac…
6feefdb 
…e, r=jieyouxu

Add more test cases for block-no-opening-brace

Also add FIXME's for rust-lang#80931 & rust-lang#78168
rust-timer added a commit to rust-lang-ci/rust that referenced this issue Sep 23, 2024
@rust-timer
Unrolled build for rust-lang#130721
df3c52d 
Rollup merge of rust-lang#130721 - GrigorenkoPV:block-no-opening-brace, r=jieyouxu

Add more test cases for block-no-opening-brace

Also add FIXME's for rust-lang#80931 & rust-lang#78168
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-diagnostics Area: Messages for errors, warnings, and lints A-parser Area: The parsing of Rust source code to an AST C-enhancement Category: An issue proposing an enhancement or a PR with one. D-papercut Diagnostics: An error or lint that needs small tweaks. P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@estebank @JohnTitor