On Mon, 26 Oct 2026 10:17:10 GMT, Jaikiran Pai <[email protected]> wrote:
> in the newer proposed change, for these specific test URIs we are now doing
> `equals()` and `compareTo()` checks.
Yes, and more: plus `hashCode()`, plus bi-directional check of each. The check
is improved from a single case (`equals()` or `compareTo()`) to 6 cases:
{equals(), compareTo(), hashCode()} × {(arg1,arg2), (arg2,arg1)}
> Is the new proposed change intentional?
Yes. For one, the old `gt(u, v)` was delegating to `lt(v, u)`. This left
`u.compareTo(v) > 0` path unchecked. Second, we increased the coverage of
`equals()`, `compareTo()`, `hashCode()`; both in their conformance with each
other, and in their behavior when the argument order is reversed. This
verification angle did not exist in the old version.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/33232#discussion_r4378978200
