[LANG-1700] Improve handling of parameterized types and variable unrolling #1549
+68
−4
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.
Summary
Fixes incorrect assignability checks for parameterized types with nested generic arguments.
Problem
TypeUtils.isAssignable()incorrectly returnedtruewhen checking ifMyComparator<Iterable<MyNonTransientException>>is assignable toMyComparator<? super MyNonTransientException>. This happened because the type variable unrolling logic ingetTypeArguments()didn't properly resolve nested generic arguments when traversing the inheritance hierarchy.Changes
getTypeArguments(): When walking up the inheritance hierarchy, now properly unrolls type variables in parameterized parent types before recursing, ensuring nested generic arguments are correctly resolvedunrollVariables(): Added avisitedset to track already-visitedTypeVariableinstances, preventing infinite loops when circular type variable references existtest_LANG_1700()validates the fix with a complex parameterized type hierarchyTest Case
The test verifies that
LexOrdering<MyNonTransientException>(which implementsMyComparator<Iterable<MyNonTransientException>>) is correctly identified as not assignable toMyComparator<? super MyNonTransientException>, sinceIterable<MyNonTransientException>is not a supertype ofMyNonTransientException.