Early loop exit in 'if' condition

Reports loops with an if statement that can end with break without changing the semantics. This prevents redundant loop iterations.

Example:

  boolean found = false;
  for (int i = 0; i < arr.length; i++) {
    if (Objects.equals(value, arr[i])) {
      found = true;
    }
  }

After the quick-fix is applied:

  boolean found = false;
  for (int i = 0; i < arr.length; i++) {
    if (Objects.equals(value, arr[i])) {
      found = true;
      break;
    }
  }

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.

IfStatementMissingBreakInLoop

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 | Performance

New in 2019.2

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 IfStatementMissingBreakInLoop

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