equals inconsistent with hashCode in AffineTransform
Martin Desruisseaux
martin.desruisseaux at geomatys.com
Mon Jul 25 13:32:40 UTC 2022
Le 25/07/2022 à 14:20, Kevin Rushforth a écrit :
> (…snip…) You can file a bug against "Client Libraries" / "2d" at
> https://bugreport.java.com/ (or find a sponsor on this list who is
> willing to file it for you), and then change the title of your PR to
> include that bug ID in the title.
I was not aware of this link, I thought that only OpenJDK committers
could fill bug reports. Thanks for the link, this is done and got
internal review ID : 9073683.
> Once your PR is RFR, you can expect that there will be some discussion
> on it, since you propose to change the implementation of equals,
> rather than limiting your change to the implementation of hashCode.
Yes this is expected. Note that change to equals method can not be
avoided since current implementation is inconsistent with itself
(A.equals(A) can return false). About how to make equals consistent with
hashCode, as said previously there is at least 2 possible ways of doing
that.
Martin
More information about the client-libs-dev
mailing list