Some classes in JavaFX override equals and hashCode, but do not specify in their docs what the new equality definition is based on (which fields).
Furthermore, some implementations are inaccurate. For example, Point2D and Point3D do floating-point equality test with ==. This does not account for NaN, +0.0 and -0.0 comparisons. If for the purpose of points we decide that -0.0==+0.0 then is should be documented. Possibly, NaN should not be allowed in the first place.
These need to be rechecked and corrected.
Furthermore, some implementations are inaccurate. For example, Point2D and Point3D do floating-point equality test with ==. This does not account for NaN, +0.0 and -0.0 comparisons. If for the purpose of points we decide that -0.0==+0.0 then is should be documented. Possibly, NaN should not be allowed in the first place.
These need to be rechecked and corrected.
- relates to
-
JDK-8290973 In AffineTransform, equals(Object) is inconsistent with hashCode()
-
- Resolved
-