[concurrency-interest] Primitives wrappers and visibility problems

Brian Goetz brian at quiotix.com
Wed Aug 23 17:57:43 EDT 2006


> If the field isn't final, it could be subject to out of order reads
> and writes, meaning that a different thread could see a partially
> created object -> not threadsafe.

Only if the object is improperly published -- published using a data 
race.  If it is properly published (statically initialized, published 
via a volatile, published/consumed with synchronization), it is 
guaranteed to work because it is effectively immutable.


More information about the Concurrency-interest mailing list