Re:Project Valhalla: A look inside Java's epic refactor
by brundolf on Sunday December 03, 2023 @02:29AM
(#38505503)
Yeah that looked like a typo (the exact opposite of what they meant to say)
Re:Project Valhalla: A look inside Java's epic refactor
by mrkeen on Sunday December 03, 2023 @03:37AM
(#38505729)
> AFAIK equals() test for equality not identity in Java.
In an ideal world, == would test for equality. In a worse world, equals() would test for equality. But we live in a Java world: Equals() is predefined as an identity check on Objects, and it's up invididual implementations to override that check with something better.
Re:Project Valhalla: A look inside Java's epic refactor
by kaba0 on Sunday December 03, 2023 @10:01AM
(#38507514)
Arguably, equality has no default, meaningful implementation. Object identity is a good default, while data-like objects=records should have the trivial equality in place. But a connection is not equal to any other, even if their internal state is equivalent.
Re:Project Valhalla: A look inside Java's epic refactor
by mrkeen on Sunday December 03, 2023 @10:54AM
(#38507962)
> Arguably, equality has no default, meaningful implementation.
> Object identity is a good default
Re:Project Valhalla: A look inside Java's epic refactor
by kaba0 on Sunday December 03, 2023 @11:11AM
(#38508090)
Is a good fallback, might have been better wording on my part.
Re:Project Valhalla: A look inside Java's epic refactor
by The_Colonel on Sunday December 03, 2023 @09:55AM
(#38507476)
The default implementation in Object class tests for identity.
AFAIK equals() test for equality not identity in Java.