-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Provide suggestion for const
argument parsed as trait object
#72273
Conversation
I'm unhappy with the cost/benefit ratio here and will try to come up with something less hacky. |
Diagnostics for the test have two orthogonal issues. The first one is
It is independent from trait objects, errors like this should probably be omitted in any of the arguments in question is poisoned by previous errors. The second one is
This looks like a material for I may be able to implement the second item myself, but not earlier than the next weekend. |
☔ The latest upstream changes (presumably #74202) made this pull request unmergeable. Please resolve the merge conflicts. |
Closing due to inactivity. |
…ng-braces, r=petrochenkov Suggest that expressions that look like const generic arguments should be enclosed in brackets I pulled out the changes for const expressions from rust-lang#71592 (without the trait object diagnostic changes) and made some small changes; the implementation is `@estebank's.` We're also going to want to make some changes separately to account for trait objects (they result in poor diagnostics, as is evident from one of the test cases here), such as an adaption of rust-lang#72273. Fixes rust-lang#70753. r? `@petrochenkov`
Split off #71592 as requested.
r? @petrochenkov