Avoid accumulating ill-kinded bounds during unification #6270
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.
This PR is a precondition for being able to enable partial unification unconditionally.
Turning partial unification on unconditionally revealed that in some error cases it was possible for the partial unification branch of
unifySpecificto add inappropriately kinded bounds to the type variablebeing solved. These later blow up in
matchingBoundsinGlbLubswhere the mismatched kinds result in aNoCommonTypeexception being thrown which crashes the compiler reporting "lub/glb of incompatible types".This commit prevents that from happening by checking that the added bounds will match the kind of the TypeVar they're being added to. If they don't then the bound is not added and unification fails.