Fix #5666: Fix normalizing map when testing for seen pairs #5675
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
When testing for seen pairs we subject both types to a "normalize" type map that derefereces LayVals. This is tricky but necessary. But we should take care that the map does not disturbe the types in any other way. In particular it should not replace a TypeVar by its instance.
odersky
added
the
fasttrack
|
I verified that this passes now with the threshold set to 9. |
OlivierBlanvillain
approved these changes
Jan 14, 2019
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.
When testing for seen pairs we subject both types to a "normalize" type map
that derefereces LayVals. This is tricky but necessary. But we should take
care that the map does not disturbe the types in any other way. In particular
it should not replace a TypeVar by its instance.