[WIP] Enforce may-define-must-define for ATPITs #123046
Closed
Conversation
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
rustbot
added
S-waiting-on-review
compiler-errors
commented
Mar 25, 2024
| @@ -78,6 +82,24 @@ impl<'tcx> RegionInferenceContext<'tcx> { | |||
| } | |||
| } | |||
| } | |||
|
|
|||
| if !infcx.tcx.is_typeck_child(anchor.to_def_id()) { | |||
There was a problem hiding this comment.
Specifically, we can't enforce this on typeck children because it would mean that the given code fails:
trait Foo {
type Assoc;
fn foo() -> Self::Assoc;
}
impl Foo for () {
type Assoc = impl Sized;
fn foo() -> Self::Assoc {
let x = || {};
// ^^^^^ <- this body doesn't define `Self::Assoc`, even though it could.
""
}
}There was a problem hiding this comment.
Do you have thoughts either, @aliemjay? 🤔
There was a problem hiding this comment.
I don't remember if this landed, but I once had a commit where opaques from children got copied into their parents during borrowck. Then we could stop looking at children entirely. Well, modulo opaques that are only mentioned in the signature of children, but... oh we don't have ATPIT tests for that, do we
There was a problem hiding this comment.
We don't collect opaques for typeck children anyways:
trait Foo {
type Assoc;
fn foo();
}
impl Foo for () {
type Assoc = impl Sized;
fn foo() {
let x = || -> Self::Assoc {
""
};
}
}error[E0308]: mismatched types
--> src/lib.rs:12:9
|
9 | type Assoc = impl Sized;
| ---------- the expected opaque type
...
12 | ""
| ^^ expected opaque type, found `&str`
|
= note: expected opaque type `<() as Foo>::Assoc`
found reference `&'static str`
There was a problem hiding this comment.
And I don't think we want to -- since if we don't, then we only need to check that the typeck root defines the given opaques.
compiler-errors
commented
Mar 25, 2024
| @@ -42,12 +43,15 @@ impl<'tcx> RegionInferenceContext<'tcx> { | |||
| /// Check that all opaque types have the same region parameters if they have the same | |||
| /// non-region parameters. This is necessary because within the new solver we perform various query operations | |||
| /// modulo regions, and thus could unsoundly select some impls that don't hold. | |||
| fn check_unique( | |||
| fn check_unique_and_defined( | |||
| @@ -78,6 +82,24 @@ impl<'tcx> RegionInferenceContext<'tcx> { | |||
| } | |||
| } | |||
| } | |||
|
|
|||
| if !infcx.tcx.is_typeck_child(anchor.to_def_id()) { | |||
There was a problem hiding this comment.
Do you have thoughts either, @aliemjay? 🤔
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
☔ The latest upstream changes (presumably #116891) made this pull request unmergeable. Please resolve the merge conflicts. |
|
OK well I'm never actually gonna work on this. Sorry @oli-obk, feel free to take over 🫡 |
3 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Putting this up in an incomplete state because I've got some concerns
r? oli-obk