-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
make Thin
a supertrait of Sized
#122553
Closed
Closed
make Thin
a supertrait of Sized
#122553
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
06a72d2
clean up fulfillment error reporting
dbdc03c
add tests for mismatched super projections with nested obligations
504da11
make `Thin` a supertrait of `Sized`
a7f12dc
always use shallow tail for metadata projections
c02b3c7
suppress errors about `T: !Thin` caused by `T: !Sized`
e399970
clippy: handle supertraits of Sized
81a8fae
miri: adjust layout cycle test to avoid overflow error
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
Oops, something went wrong.
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.
I wonder if we can just use
error_fixed_by
everywhere -- it seems more general thanerror_implied_by
?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.
Not necessarily in this PR, but maybe tracked as a FIXME.
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.
That's what I tried first, but there are multiple problems with this approach:
error_fixed_by
does not work when there are any infer vars incond
(first arg). This adds a lot of duplicate diagnostics.A fixed-by B
+not (B fixed-by A)
+B fixed-by C
+not (C fixed-by B)
+C fixed-by A
+not (A fixed-by C)
. In these cases, replacingerror_implied_by
witherror_fixed_by
causes no diagnostics to be emitted. This cannot happen witherror_implied_by
, becauseA implied-by B
is transitive.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.
After thinking about this again, I'm actually not sure anymore whether this can actually happen and can't come up with a concrete example. I had a test failing and thought that was due a cycle like that, but after trying it again it turned out to be an unrelated implementation bug.