Overly large initializer for array of primitive type
Reports array initializer expressions for primitive arrays that contain too many elements. Such initializers may result in overly large class files because code must be generated to initialize each array element. In memory or bandwidth constrained environments, it may be more efficient to load large arrays of primitives from resource files.
This inspection is intended for Java ME and other highly resource constrained environments. Applying the results of this inspection without consideration might have negative effects on code clarity and design.
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.
OverlyLargePrimitiveArrayInitializer- 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 specify the maximum number of elements to allow in primitive array initializers.
Inspection options
Here you can find the description of settings available for the Overly large initializer for array of primitive type inspection, and the reference of their default values.
- Maximum number of elements
64
Inspection Details | |
|---|---|
By default bundled with: | |
Can be installed with plugin: | Java, 243.23126 |