RFR: JDK-8074578 Document memory visibility effects of some Unsafe methods

[Martin Buchholz]

On Wed, Mar 11, 2015 at 2:12 AM, Paul Sandoz <paul.sandoz at oracle.com> wrote:

>
> I am all for clearing up the language here, but think it prudent to hold
> off doing much until the language for JMM revisions and VarHandle is
> produced, then we can revisit.
>

I'm disappointed we can't add such a small and safe doc fix now.

I agree the public docs for replacements for Unsafe methods will be much
harder (and more important) to get right.  Especially if they include
wording and API that help those familiar with C/C++11 atomics, as I would
like.