-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Replace the obligation forest with a graph #33491
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
957500b
rewrite obligation forest. cycles still handled incorrectly.
5c39a2a
add cycle-reporting logic
arielb1 f0f5ef5
address review comments
arielb1 5458d8b
rewrite fuzzy `on_unimplemented` matching to avoid ICEs
arielb1 65ad935
change on_unimplented logic
arielb1 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
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.
so, while I do prefer this simplified approach, it seems like it would mean that
vec[3_i32]
will fail to get the "helpful message" we were shooting for? (I could be confused; I'll kick off a local build and check it out)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 sure how the earlier approach worked for that. EDIT: that never worked.
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.
both approaches do not report a helpful error message when a
Vec
is involved. Unless we are willing to add a "useless"impl Index<usize> for Vec
, I don't see how this can be solved.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 guess I just mean slice, then. There is this test:
check_on_unimplemented_on_slice.rs
which fails.The fact that this doesn't work for vec (if indeed true) suggests that we may want to tie the hint to the use of the
[]
syntax rather than having a more generic mechanism, honestly.I tend to think that the "on unimplemented" mechanism may need some work in any case. For example, I think the hint would be a bit confusing when you have
X: Index<u32>
and you supply a slice. (I have often found the "on unimplemented" messages from other traits confusing for this reason.)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 just my logic being stupid. I have a fix to that.