-
Notifications
You must be signed in to change notification settings - Fork 13.3k
WIP: Normalize associated types in structs when performing unsizing coercion #87548
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
Closed
Closed
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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
// check-pass | ||
|
||
trait Trait {} | ||
|
||
impl<T0> Trait for T0 {} | ||
|
||
impl<T1: ?Sized> Id for T1 { | ||
type Assoc = T1; | ||
} | ||
|
||
trait Id { | ||
type Assoc: ?Sized; | ||
} | ||
|
||
struct NewType<T2: ?Sized + Id>(T2::Assoc); | ||
|
||
fn coerce_newtype_slice<'a, T3, const N: usize>(array: &'a NewType<[T3; N]>) -> &'a NewType<[T3]> { | ||
array | ||
} | ||
|
||
fn coerce_newtype_trait<T4: Trait + 'static>(tr: &NewType<T4>) -> &NewType<dyn Trait> { | ||
tr | ||
} | ||
|
||
fn main() { | ||
let nt = NewType::<[i32; 1]>([0]); | ||
coerce_newtype_slice(&nt); | ||
coerce_newtype_trait(&nt); | ||
} |
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.
Why is this commented out? We definitely shouldn't drop these obligations.
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.
This is very WIP and actually even abandoned 😅
At the time, I was experimenting with this and was hitting problems I couldn't understand, so I was commenting out different parts in an attempt to understand what and how (doesn't) work.
We've discussed this with Niko in a zulip thread and he said that it would probably be better to remove the "special trait solver" altogether:
I wanted to work on this (the issue I'm trying to fix really bothers me), but this never ended up happening.
I can try to revive this PR or try to make the refactor Niko proposed. But I'd need some guidance since I haven't worked on the compiler much before, so I'm not sure if I'll help or just spend someones time 😅
I'm assuming since you've assigned yourself, you know this part of the compiler well?