Why is this an issue?

When the call to a function doesn’t have any side effects, what is the point of making the call if the results are ignored? In such case, either the function call is useless and should be dropped or the source code doesn’t behave as expected.

To prevent generating any false-positives, this rule triggers an issue only on the following predefined list of immutable classes in the Java API :

As well as methods of the following classes:

Noncompliant code example

public void handle(String command){
  command.toLowerCase(); // Noncompliant; result of method thrown away
  ...
}

Compliant solution

public void handle(String command){
  String formattedCommand = command.toLowerCase();
  ...
}

Exceptions

This rule will not raise an issue when both these conditions are met:

private boolean textIsInteger(String textToCheck) {

    try {
        Integer.parseInt(textToCheck, 10); // OK
        return true;
    } catch (NumberFormatException ignored) {
        return false;
    }
}

Resources