On Mar 19, 2014, at 4:32 PM, Mike Duigou <mike.dui...@oracle.com> wrote:
> Since the Unsafe.getObjectVolatile() allows use of volatile semantics without > having to declare the field volatile I think this is a better idiom than what > I had previously suggested. Hopefully this is a pattern we can use elsewhere. > > Are the java.util.concurrent.atomic imports still needed? No they are not. I can remove them (and move the code at lines 2897-2906 to following coding conventions) if this is eventually approved. > I have not reviewed the other changes. Aside from toString() they are mostly straightforward cleanup. Thanks, Brian
