-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Warnings for Issue 32330 #33105
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
nikomatsakis
wants to merge
10
commits into
rust-lang:master
from
nikomatsakis:issue-32330-lbr-in-return-type-warning
Closed
Warnings for Issue 32330 #33105
nikomatsakis
wants to merge
10
commits into
rust-lang:master
from
nikomatsakis:issue-32330-lbr-in-return-type-warning
Conversation
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 is a step towards fixing rust-lang#32330. The full fix would be a breaking change, so we begin by issuing warnings for scenarios that will break.
We ought not to be affecting inference state when assembling candidates, so invoke select inside of a probe.
Before we would ignore a candidate if it happened to be an impl with a default type. This change makes us never add the impl in the first place. This seems largely equivalent, though there might be some subtle difference in that -- before -- we would have failed to normalize if there was a "trait-def-candidate" contending with an (opaque) impl candidate. This corresponds I guess to a case like `<<A as Trait>::B as Trait2>::C`, and the definition of `Trait` contains a clause. Pretty obscure, but it seems like it's... ok to favor the trait definition in such a case.
Actually, I'll just re-open the original PR, duh. |
Oh, GH won't let me do that anymore. Oh well. |
@bors r=aturon |
📌 Commit 3449575 has been approved by |
@bors r- |
Remembered I wanted to update the issue number. |
Actually I lied. I will submit an expanded version of this branch after all that issues more warnings. |
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.
This code was already reviewed by @aturon in #32488. I was planning on incorporating it into a bigger PR but decided it'd be better to land it first after all.
r? @aturon