Add regression test for type variable collision across interfaces#36900
Open
pavanB247 wants to merge 1 commit into
Open
Add regression test for type variable collision across interfaces#36900pavanB247 wants to merge 1 commit into
pavanB247 wants to merge 1 commit into
Conversation
spring-projects-issues
added
the
status: waiting-for-triage
Signed-off-by: pavanB247 <135733563+pavanB247@users.noreply.github.com>
pavanB247
force-pushed
the
fix-generic-typevar-collision
branch
from
ad05c7a to
043c3f3
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 commit adds a regression test for a type variable collision scenario across multiple interfaces.
The test verifies generic type resolution when multiple interfaces declare type variables with the same name and are implemented by the same class.
The added test ensures that GenericTypeResolver.resolveType(...) continues to resolve the expected type in this scenario.