[concurrency-interest] Should I avoid compareAndSet with value-based classes?

Kirk Pepperdine kirk at kodewerk.com
Wed Jul 12 06:18:16 EDT 2017

> On Jul 12, 2017, at 1:15 PM, Stephen Colebourne <scolebourne at joda.org> wrote:
> As the author of Instant, what I would really like is for == to mean
> .equals().

Really? There is a definitive semantic difference between == and equals() and I’m trying to sort out why anyone would want to confuse them.

Kind regards,

More information about the Concurrency-interest mailing list