RFR: 8290973: In AffineTransform, equals(Object) is inconsistent with hashCode()
Dio Brando
duke at openjdk.org
Fri Aug 5 14:49:52 UTC 2022
On Fri, 10 Jun 2022 09:39:48 GMT, Martin Desruisseaux <duke at openjdk.org> wrote:
> `AffineTransform.equals(Object)` and `hashCode()` break two contracts:
>
> * `A.equals(A)` returns `false` if at least one affine transform coefficient is NaN.
> * `A.equals(B)` should imply `A.hashCode() == B.hashCode()`, but it is not the case if a coefficient is zero with an opposite sign in A and B.
>
> This patch preserves the current behaviour regarding 0 (i.e. -0 is considered equal to +0) for backward compatibility reason. Instead the `hashCode()` method is updated for being consistent with `equals(Object)` behaviour.
Have you checked all tests ? I did not see it
-------------
PR: https://git.openjdk.org/jdk/pull/9121
More information about the client-libs-dev
mailing list