Collection without initial capacity
Reports attempts to instantiate a new Collection
object without specifying an initial capacity.
If no initial capacity is specified, a default capacity is used, which will rarely be optimal. Failing to specify initial capacities for collections may result in performance issues if space needs to be reallocated and memory copied when the initial capacity is exceeded. This inspection checks allocations of classes listed in the inspection's settings.
Example:
Use the following options to configure the inspection:
List collection classes that should be checked.
Whether to ignore field initializers.
Inspection options
Option | Type | Default |
---|---|---|
Classes to check | StringList | [java.util.ArrayDeque, java.util.ArrayList, java.util.BitSet, java.util.HashMap, java.util.HashSet, java.util.Hashtable, java.util.IdentityHashMap, java.util.LinkedHashMap, java.util.LinkedHashSet, java.util.PriorityQueue, java.util.Vector, java.util.WeakHashMap, java.util.concurrent.ConcurrentHashMap, java.util.concurrent.PriorityBlockingQueue] |
Don't report field initializers | Checkbox | false |
Inspection Details | |
---|---|
Available in: | IntelliJ IDEA 2023.3, Qodana for JVM 2023.3 |
Plugin: | Java, 233.SNAPSHOT |