Golang memory model and read/write barrier

<p>I&#39;ve read golang memory model doc.<a href="https://golang.org/ref/mem" rel="nofollow">https://golang.org/ref/mem</a>. Looks like golang introduce a different semantics for read/write barrier. Coming from a java background, I only know <code>volatile</code> keyword and memory barrier, not the diff between read/write. How are these two difference? </p> <hr/>**评论：**<br/><br/>tv64738: <pre><p>Forget all about barriers and volatile.</p> <p>B can observe what was done by A if there is a happens-before relationship from A to B.</p></pre>