-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Don't consider candidates with no failing where clauses when refining obligation causes in new solver #124771
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
22 changes: 22 additions & 0 deletions
22
tests/ui/traits/next-solver/diagnostics/where-clause-doesnt-apply.rs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
trait Foo {} | ||
trait Bar {} | ||
|
||
impl<T> Foo for T where T: Bar {} | ||
fn needs_foo(_: impl Foo) {} | ||
|
||
trait Mirror { | ||
type Mirror; | ||
} | ||
impl<T> Mirror for T { | ||
type Mirror = T; | ||
} | ||
|
||
// Make sure the `Alias: Foo` bound doesn't "shadow" the impl, since the | ||
// impl is really the only candidate we care about here for the purpose | ||
// of error reporting. | ||
fn hello<T>() where <T as Mirror>::Mirror: Foo { | ||
needs_foo(()); | ||
//~^ ERROR the trait bound `(): Foo` is not satisfied | ||
} | ||
|
||
fn main() {} |
22 changes: 22 additions & 0 deletions
22
tests/ui/traits/next-solver/diagnostics/where-clause-doesnt-apply.stderr
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
error[E0277]: the trait bound `(): Foo` is not satisfied | ||
--> $DIR/where-clause-doesnt-apply.rs:18:15 | ||
| | ||
LL | needs_foo(()); | ||
| --------- ^^ the trait `Bar` is not implemented for `()`, which is required by `(): Foo` | ||
| | | ||
| required by a bound introduced by this call | ||
| | ||
note: required for `()` to implement `Foo` | ||
--> $DIR/where-clause-doesnt-apply.rs:4:9 | ||
| | ||
LL | impl<T> Foo for T where T: Bar {} | ||
| ^^^ ^ --- unsatisfied trait bound introduced here | ||
note: required by a bound in `needs_foo` | ||
--> $DIR/where-clause-doesnt-apply.rs:5:22 | ||
| | ||
LL | fn needs_foo(_: impl Foo) {} | ||
| ^^^ required by this bound in `needs_foo` | ||
|
||
error: aborting due to 1 previous error | ||
|
||
For more information about this error, try `rustc --explain E0277`. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kind of a shame we have to do this in a probe, but if we don't, then the instantiated nested goals from different candidates will affect eachother, causing weirdness and ICEs.
Luckily, we do this only when there's >1 candidate.
We could, perhaps, first filter out candidates with no
GoalSource::ImplWhereBound | GoalSource::InstantiateHigherRanked
without even instantiating them, and only instantiate them if necessary.Also, I guess we should have both the source and the certainty in the proof tree without instantiating -- we just need to expose it, perhaps?