Java
Non-final field referenced in 'hashCode()'
Warning
New
Last modified: 03 December 2024 Reports implementations of hashCode()
that access non-final
variables.
Such access may result in hashCode()
returning different values at different points in the object's lifecycle, which may in turn cause problems when using the standard collections classes.
Example:
class Drink {
String name;
Drink(String name) { this.name = name; }
@Override public int hashCode() {
return Objects.hash(name); //warning
}
}
...
Drink coffee = new Drink("Coffee");
priceMap.put(coffee, 10.0);
coffee.name = "Tea";
double coffeePrice = priceMap.get(coffee); //not found
A quick-fix is suggested to make the field final:
class Drink {
final String name;
...
}
- 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.
NonFinalFieldReferencedInHashCode
Inspection Details | |
---|---|
By default bundled with: | |
Can be installed with plugin: | Java, 243.23126 |
Thanks for your feedback!
Was this page helpful?