-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Don't call type_of
on TAIT in defining scope in new solver
#112825
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
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 was deleted.
Oops, something went wrong.
16 changes: 16 additions & 0 deletions
16
tests/ui/traits/new-solver/dont-type_of-tait-in-defining-scope.not_send.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,16 @@ | ||
error[E0283]: type annotations needed: cannot satisfy `Foo: Send` | ||
--> $DIR/dont-type_of-tait-in-defining-scope.rs:16:5 | ||
| | ||
LL | needs_send::<Foo>(); | ||
| ^^^^^^^^^^^^^^^^^ | ||
| | ||
= note: cannot satisfy `Foo: Send` | ||
note: required by a bound in `needs_send` | ||
--> $DIR/dont-type_of-tait-in-defining-scope.rs:13:18 | ||
| | ||
LL | fn needs_send<T: Send>() {} | ||
| ^^^^ required by this bound in `needs_send` | ||
|
||
error: aborting due to previous error | ||
|
||
For more information about this error, try `rustc --explain E0283`. |
22 changes: 22 additions & 0 deletions
22
tests/ui/traits/new-solver/dont-type_of-tait-in-defining-scope.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 @@ | ||
// revisions: is_send not_send | ||
// compile-flags: -Ztrait-solver=next | ||
//[is_send] check-pass | ||
|
||
#![feature(type_alias_impl_trait)] | ||
|
||
#[cfg(is_send)] | ||
type Foo = impl Send; | ||
|
||
#[cfg(not_send)] | ||
type Foo = impl Sized; | ||
|
||
fn needs_send<T: Send>() {} | ||
|
||
fn test() { | ||
needs_send::<Foo>(); | ||
//[not_send]~^ ERROR type annotations needed: cannot satisfy `Foo: Send` | ||
} | ||
|
||
fn main() { | ||
let _: Foo = (); | ||
} |
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.
I personally don't like this perspective on why we do this. Imo the query cycles are a side effect of something more fundamental:
instantiate_constituent_tys_for_auto_trait
for opaque types is a hacky, pseudo normalization-routine which does not check item bounds of the opaqueReveal::All
, using regular normalization is strictly preferable to auto trait leakageI would like you to rewrite this comment to reflect that, but also fine to wait and chat about it in sync a bit if you don't consider this perspective to be helpful or maybe even correct
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.
I'm not particularly attached to any specific comment here, though I think the best way to settle this is for you to just write what you'd like for this comment to say as an inline suggestion.
I'm not sure if we share the exact mental model for why this "hack" is not as much of a hack as it seems, but what I wrote above is how I see it at least from an implementation perspective.
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.
the comment I would like to write would also require some general code changes, put that in my notes and will look at it at some later point and open a separate PR