Skip to content

Parsing of ? opt-out trait bounds doesn't match rustc #12442

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
Closed
jonas-schievink opened this issue Jun 1, 2022 · 0 comments · Fixed by #12444
Closed

Parsing of ? opt-out trait bounds doesn't match rustc #12442

jonas-schievink opened this issue Jun 1, 2022 · 0 comments · Fixed by #12444
Labels
A-parser parser issues C-bug Category: bug S-actionable Someone could pick this issue up and work on it right now

Comments

@jonas-schievink
Copy link
Contributor

This is valid code, but rust-analyzer doesn't parse it correctly:

fn f<T>() where T: ?for<> Sized {}
@jonas-schievink jonas-schievink added S-actionable Someone could pick this issue up and work on it right now A-parser parser issues C-bug Category: bug labels Jun 1, 2022
@xffxff xffxff mentioned this issue Jun 1, 2022
Merged
@bors bors closed this as completed in 88024c7 Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-parser parser issues C-bug Category: bug S-actionable Someone could pick this issue up and work on it right now
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: parsing of ? opt-out trait bounds xffxff/rust-analyzer
1 participant
@jonas-schievink