Lambda parameter hides field

Reports lambda parameters named identically to a field of a surrounding class. As a result of such naming, you may accidentally use the lambda parameter when using the identically named field is intended.

A quick-fix is suggested to rename the lambda parameter.

Example:

  public class MyClass {
    public Object foo;

    void sort(List<Integer> list) {
      list.sort((foo, bar) -> foo - bar);
    }
  }

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

LambdaParameterHidesMemberVariable

Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | Java | Visibility

Use the option to choose whether to ignore fields that are not visible from the lambda expression. For example, private fields of a superclass.

This inspection depends on the Java feature 'Lambda expressions', which is available since Java 8.

Inspection options

Here you can find the description of settings available for the Lambda parameter hides field inspection, and the reference of their default values.

Ignore fields not actually visible from the lambda: Default value:
Selected

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection LambdaParameterHidesMemberVariable

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

IntelliJ IDEA 2025.2

Inspection Details
By default bundled with:	IntelliJ IDEA 2025.2, Qodana for JVM 2025.2,

Last modified: 18 September 2025