-
Notifications
You must be signed in to change notification settings - Fork 13.9k
Do not emit solver errors that contain error types #148290
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
base: master
Are you sure you want to change the base?
Conversation
|
r? @nnethercote rustbot has assigned @nnethercote. Use |
This comment has been minimized.
This comment has been minimized.
cf530bd to
d5123f6
Compare
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
Seems reasonable - the presence of an error type means that there will be some diagnostic emitted, and that's likely going to be closer to the "root cause" |
any follow-up errors are going to either be duplicates or often disappear if the error itself is fixed.
in this PR it mostly silences dyn-compat errors as all the other errors are already deduplicated outside of the test suite. The dyn compat errors are independent errors and I think if the dyn compatiblity depended on an error type it would not actually show, so this is PR is actually silencing independent errors, too.
I am opening this PR because I am seeing lots of
{type error}: const Traiterrors when adding more const checking. So instead of targetting just those specific errors, I wanted to try out fully avoiding such errors near the trait solver.cc @rust-lang/types for thoughts