-
Notifications
You must be signed in to change notification settings - Fork 13.9k
Do two passes of handle_opaque_type_uses_next
#147249
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
+118
−49
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
db3c9b6
When computing opaque types in the next solver, take an initial pass …
jackh726 9a5cef1
Cleanup opaque_type computation a bit
jackh726 c6c58e3
Remove UsageKind::HasError
jackh726 a3fbae5
Merge match and if
jackh726 283ad66
Fix comment, change first_pass to error_on_missing_defining_use, remo…
jackh726 8b17827
Remove unneeded get_hidden_type
jackh726 d51f09e
Review comments. Move resolve_vars_if_possible into fn and add test m…
jackh726 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
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
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
44 changes: 44 additions & 0 deletions
44
tests/ui/traits/next-solver/opaques/hidden-types-equate-before-fallback.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,44 @@ | ||
//@ revisions: current next | ||
//@ ignore-compare-mode-next-solver (explicit revisions) | ||
//@[next] compile-flags: -Znext-solver | ||
//@ check-pass | ||
|
||
// Regression test for trait-system-refactor-initiative#240. Hidden types should | ||
// equate *before* inference var fallback, otherwise we can get mismatched types. | ||
|
||
jackh726 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
#[derive(Clone, Copy)] | ||
struct FileSystem; | ||
impl FileSystem { | ||
fn build<T>(self, commands: T) -> Option<impl Sized> { | ||
match false { | ||
true => Some(commands), | ||
false => { | ||
drop(match self.build::<_>(commands) { | ||
Some(x) => x, | ||
None => return None, | ||
}); | ||
panic!() | ||
}, | ||
} | ||
} | ||
} | ||
|
||
fn build2<T, U>() -> impl Sized { | ||
if false { | ||
build2::<U, T>() | ||
} else { | ||
loop {} | ||
}; | ||
1u32 | ||
} | ||
|
||
fn build3<'a>() -> impl Sized + use<'a> { | ||
if false { | ||
build3() | ||
} else { | ||
loop {} | ||
}; | ||
1u32 | ||
} | ||
|
||
fn main() {} |
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.
we can also just go from no uses to a defining use due to fallback, e.g. if you have soem
?will_fallback: Trait<opaque>
goalThere 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.
That is
UnconstrainedHiddleType
?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.
it could also be
None
. Maybe not with this specific example, but certainly with?will_fallback: RequiresSend<fn_ptr_to_opaque>