Fix normalization involving bound regions #22785
Merged
Conversation
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
| //! | ||
| //! <T as Trait> <: <U as Trait> | ||
| //! | ||
| //! means that if I know that `T as Trait`, |
There was a problem hiding this comment.
heh, what the heck happened to your emacs fill-paragraph settings here...
There was a problem hiding this comment.
oh, I originally wrote that in a different location. I tried to refill all the paragraphs but I guess I missed one :)
Manishearth
added a commit
to Manishearth/rust
that referenced
this pull request
Feb 25, 2015
…ion-with-regions, r=pnkfelix Two changes: 1. Make traits with assoc types invariant w/r/t their inputs. 2. Fully normalize parameter environments, including any region variables (which were being overlooked). The former supports the latter, but also just seems like a reasonably good idea. Fixes rust-lang#21750 cc @edwardw r? @pnkfelix
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.
Two changes:
The former supports the latter, but also just seems like a reasonably good idea.
Fixes #21750
cc @edwardw
r? @pnkfelix