'StringBuilder' without initial capacity
Reports attempts to instantiate a new StringBuffer or StringBuilder object without specifying its initial capacity.
If no initial capacity is specified, a default capacity is used, which will rarely be optimal. Failing to specify the initial capacity for StringBuffer may result in performance issues if space needs to be reallocated and memory copied when the initial capacity is exceeded.
Example:
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.
StringBufferWithoutInitialCapacity- 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.
Inspection Details | |
|---|---|
By default bundled with: | |
Can be installed with plugin: | Java, 243.23126 |