[concurrency-interest] AtomicReferenceFieldUpdater vs Unsafe

Doug Lea dl at cs.oswego.edu
Thu Nov 17 07:55:09 EST 2011

On 11/17/11 07:49, √iktor Ҡlang wrote:
>     Portability of Unsafe constructions is not really a problem.
>     We frequently communicate with all production JVM implementors
>     to help ensure that they are correctly supported.
> Alright, that's a good clarification, I've always avoided it from compatibility
> reasons.
> Is this case the same with Android?

Android runs unmodified java.util.concurrent, so at least supports
the Unsafe methods that we use.


More information about the Concurrency-interest mailing list