unique even if two objects happen to be allocated at the same memory address during app’s lifetime.
Would it make sense to file this as a bug (it’s a noticeable discrepancy with JVM, after all) or is it a conscious decision to have this implementation in Native?
e
ephemient
05/12/2022, 12:09 PM
Java does not require that identityHashCode is a random value; some implementations of JVM use memory address (although modern versions of OpenJDK does not, by default)