Fix circularity issue when checking multiple generic interface constraints. #6121
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.
We need to defer the checking of the super-type of a constraint to after we ascertain that the sub-type is relevant to the current call.
Otherwise, the checking of any constraint in a generic will trigger the checking of all other constraints & can lead to a scenario where the super-type depends on a type whose inheritance info is currently being created.
Since inheritance info is initialized to empty set, this will produce an incorrect isSubtype result & cause an error during checking.
Seems to only occur if more than 1 generic interface constraint is present.