Fix #7526: Don't check class info within bounds when taking denotions #7560
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
…enotations When computing a denotation, always assume that ClassInfos override TypeBounds and other ClassInfos. RefChecks will verify later that the overrides are legal. This is needed to prevent infinite recursion involving interleaved subtype checks and denotation computations prompted by findMember.
smarter
approved these changes
Nov 25, 2019
Co-Authored-By: Guillaume Martres <smarter@ubuntu.com>
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 computing a denotation, always assume that ClassInfos override TypeBounds
and other ClassInfos. RefChecks will verify later that the overrides are legal.
This is needed to prevent infinite recursion involving interleaved subtype checks
and denotation computations prompted by findMember.