On Sun, 6 Sep 2026 03:59:35 GMT, Yunbo Zhang <[email protected]> wrote:
> Thanks for pointing this out. The existing equals/hashCode issue is tracked > by [JDK-8362427](https://bugs.openjdk.org/browse/JDK-8362427) and is > currently in progress. This change would expose another instance with "1" and > "1+0". As ExE-Boss notes, there is a long standing issue with equals/hashCode. I'm concerned about introducing more cases. Just some context here: ModuleDescriptor.Version is unfinished business and there are both specification and implementation issues that need consideration. In JDK 9 we decided to leave it "as is" to allow focusing on more important module system issues. I'm wondering if it's a good or bad idea to touch it with a drive-by fix. Do you mind saying if ran into a library that had a versioning policy that runs into this? Or is this just taking an open issue in JBS. ------------- PR Comment: https://git.openjdk.org/jdk/pull/32715#issuecomment-5560663702
