-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Canonicalize root var when making response from new solver #108839
Merged
bors
merged 2 commits into
rust-lang:master
from
compiler-errors:canonicalize-the-root-var
Mar 9, 2023
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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 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
This file contains 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
This file contains 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
This file contains 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
39 changes: 39 additions & 0 deletions
39
tests/ui/traits/new-solver/canonical-ty-var-eq-in-response.rs
This file contains 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,39 @@ | ||
// check-pass | ||
// compile-flags: -Ztrait-solver=next | ||
|
||
trait Mirror { | ||
type Item; | ||
} | ||
|
||
struct Wrapper<T>(T); | ||
impl<T> Mirror for Wrapper<T> { | ||
type Item = T; | ||
} | ||
|
||
fn mirror<T>() | ||
where | ||
Wrapper<T>: Mirror<Item = i32>, | ||
{ | ||
} | ||
|
||
fn main() { | ||
mirror::<_ /* ?0 */>(); | ||
|
||
// Solving `<Wrapper<?0> as Mirror>::Item = i32` | ||
|
||
// First, we replace the term with a fresh infer var: | ||
// `<Wrapper<?0> as Mirror>::Item = ?1` | ||
|
||
// We select the impl candidate on line #6, which leads us to learn that | ||
// `?0 == ?1`. | ||
|
||
// That should be reflected in our canonical response, which should have | ||
// `^0 = ^0, ^1 = ^0` | ||
// !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | ||
// !! We used to return a totally unconstrained response here :< !! | ||
// !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | ||
|
||
// Then, during the "equate term" part of the projection solving, we | ||
// instantiate the response from the unconstrained projection predicate, | ||
// and equate `?0 == i32`. | ||
} |
This file contains 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,6 @@ | ||
// check-pass | ||
// compile-flags: -Ztrait-solver=next | ||
|
||
fn main() { | ||
let x: Box<dyn Iterator<Item = ()>> = Box::new(std::iter::empty()); | ||
} |
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.
Both of these UI tests I added in the PR fail here. That's because the inference guidance we applied from a
Certainty::AMBIGUOUS
response can make the goal pass the next time it's evaluated.This seems like it's to be expected though, as long as we're returning canonical var values in ambiguous responses 🤔
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.
shouldn't be, the issue again that the solver proves goals in sequence and doesn't reprove previous goals.
I guess disabling it for now is alright but I do want us to get to a point where we always internally keep reproving goals until we hit a fixpoint