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));
}
- 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
Use the option to ignore calls to common Java iteration methods like Iterator.hasNext()
and known methods with side-effects like Atomic*.compareAndSet
.
Here you can find the description of settings available for the Method call in loop condition inspection, and the reference of their default values.
Inspection Details | |
---|---|
By default bundled with: | |
Can be installed with plugin: | Java, 243.23126 |
Thanks for your feedback!