Versions: SonarQube Version 6.7.1 (build 35068), SonarJava: 5.4 (build 14284) In this situation, Sonar suggests to replace the lambda by a method reference. It is however not possible since there are two methods matching: Integer.toString() and Integer.toString(int). Set<Integer> tempSet = new Has…

Hello, you are right that rule S1612 doesn’t handle possible ambiguity of method reference. I created ticket to fix this issue SONARJAVA-2795 . In your concrete case one can also avoid ambiguity by using Object::toString Thanks for reporting this issue.

S1612 should not complain if method reference is ambiguous

Rules and Languages Report False-positive / False-negative...

saberduck (Tibor Blenessy) Split this topic April 29, 2020, 10:44am 3

A post was split to a new topic: Potential FP on S1612

Topic		Replies	Views
Suggestion to replace lambda with method reference causes invalid code (java:S1612) Report False-positive / False-negative... java , eclipse , spring	2	1586	September 26, 2022
S1612 recommends to turn a lambda into a method reference, even if the result is not equivalent Report False-positive / False-negative... java , sonarqube-ide	1	445	September 27, 2021
FP java:S1612 Replace lambda with ::cast Report False-positive / False-negative... java	1	24	November 21, 2024
Potential FP on S1612 Report False-positive / False-negative... java	3	504	May 14, 2020
S1612: Class name in method reference can be irrelevant Report False-positive / False-negative... java	1	731	December 6, 2021

S1612 should not complain if method reference is ambiguous

Related topics