-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Warnings for Issue 32330 #33105
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
Commits on Apr 20, 2016
-
Configuration menu - View commit details
-
Copy full SHA for c8b2d18 - Browse repository at this point
Copy the full SHA c8b2d18View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4bfef5c - Browse repository at this point
Copy the full SHA 4bfef5cView commit details -
warn if bindings/return-types reference regions
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.
Configuration menu - View commit details
-
Copy full SHA for d05a49c - Browse repository at this point
Copy the full SHA d05a49cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4aeadfa - Browse repository at this point
Copy the full SHA 4aeadfaView commit details -
refactor: use
select
inside of a probeWe ought not to be affecting inference state when assembling candidates, so invoke select inside of a probe.
Configuration menu - View commit details
-
Copy full SHA for a03707d - Browse repository at this point
Copy the full SHA a03707dView commit details -
no candidate for impl with default type
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.
Configuration menu - View commit details
-
Copy full SHA for c3c80aa - Browse repository at this point
Copy the full SHA c3c80aaView commit details -
Configuration menu - View commit details
-
Copy full SHA for a9ffef8 - Browse repository at this point
Copy the full SHA a9ffef8View commit details -
Configuration menu - View commit details
-
Copy full SHA for beae6c7 - Browse repository at this point
Copy the full SHA beae6c7View commit details -
Configuration menu - View commit details
-
Copy full SHA for cf12a79 - Browse repository at this point
Copy the full SHA cf12a79View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3449575 - Browse repository at this point
Copy the full SHA 3449575View commit details
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.