[jmm-dev] weakCompareAndSet memory semantics

[Justin Sampson]

Howdy,

Some existing JDK methods named "compareAndSet" already allow
spurious failure while providing volatile semantics on success,
which has always struck me as entirely fine and desirable. Is
documentation of those cases being worked into this wave of
enhancements?

See the thread "Varieties of CAS semantics (another doc fix
request)" here:

http://cs.oswego.edu/pipermail/concurrency-interest/2015-January/thread.html#13613

Cheers,
Justin

P.S. The existing compareAndSet methods I'm referring to are the
ones on AtomicStampedReference and AtomicMarkableReference.