[java] Fix #5043: FP in LambdaCanBeMethodReference when method ref would be ambiguous #6285
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
Use similar approach as UseDiamondOperator, replay inference with a faked expr mirror to check that replacing lambda with method ref would be valid. Fix pmd#5043 Fix a TODO in type resolution codebase that was causing ambiguity errors with method references. Potential compatibility of method refs was not checked properly.
f6ec44f to
18da69c
Compare
Contributor
|
Compared to main: (comment created at 2025-12-01 10:52:52+00:00 for 18da69c) |
adangel
added a commit
that referenced
this pull request
Dec 18, 2025
adangel
added a commit
that referenced
this pull request
Dec 18, 2025
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.
Use similar approach as UseDiamondOperator, replay inference with a faked expr mirror to
check that replacing lambda with method ref would be valid.
Fix a TODO in type resolution codebase that was causing ambiguity errors with method references.
Potential compatibility of method refs was not checked properly.
Related issues
Ready?
./mvnw clean verifypasses (checked automatically by github actions)