On 22/01/16 00:01, Vitaly Davidovich wrote:
> I think the get/setOpaque methods need a bit more explanation ("opaque" is
> an odd naming choice, IMO). Specifically, it says the operations are done
> in program order but have no effect on inter-thread ordering/visibility.
> Is this spec verbiage for a full compiler-only fence?It's like C++ memory_order_relaxed, I guessed. I understand that but not "opaque". Andrew.
