Object comparison using '==', instead of 'equals()'
Reports code that uses == or != rather than equals() to test for object equality.
Comparing objects using == or != is often a bug, because it compares objects by identity instead of equality. Comparisons to null are not reported.
Array, String and Number comparisons are reported by separate inspections.
Example:
After the quick-fix is applied:
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.
ObjectEquality- 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 inspection settings to configure exceptions for this inspection.
Inspection options
Here you can find the description of settings available for the Object comparison using '==', instead of 'equals()' inspection, and the reference of their default values.
- Ignore '==' between enum variables
Default value:
Selected- Ignore '==' between final class types without 'equals()' implementation
Default value:
Selected- Ignore '==' between objects of a type with only 'private' constructors
Default value:
Not selected
Suppressing Inspection
You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: |