Method call in loop condition

Reports method calls in the condition part of a loop statement. In highly resource constrained environments, such calls may have adverse performance implications.

Applying the results of this inspection without consideration might have negative effects on code clarity and design. This inspection is intended for Java ME and other highly resource constrained environments.

Example:

  String s = "example";
  for (int i = 0; i < s.length(); i++) {
    System.out.println(s.charAt(i));
  }

After the quick-fix is applied:

  String s = "example";
  int length = s.length();
  for (int i = 0; i < length; i++) {
    System.out.println(s.charAt(i));
  }

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.

MethodCallInLoopCondition

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.

Use the option to ignore calls to common Java iteration methods like Iterator.hasNext() and known methods with side-effects like Atomic*.compareAndSet.

Inspection options

Here you can find the description of settings available for the Method call in loop condition inspection, and the reference of their default values.

Ignore known methods with side-effects: Default: Selected

Availability

By default bundled with: IntelliJ IDEA 2024.1, Qodana for JVM 2024.1,
Can be installed with plugin: Java, 241.18072

Last modified: 18 June 2024