&gt; which means that the memory will always be safe to use<p>In another post [1], the author of the article claims that Go will not &quot;tolerate unsafe memory access&quot;.<p>A reference to a variable could be sent across a channel and nil&#x27;d from the sending goroutine before being dereferenced in the recipient goroutine, causing a crash.  Doesn&#x27;t this invalidate the &quot;safe memory&quot; claims, or are concurrency-related memory issues not considered when making that claim?<p>[1] <a href="http:&#x2F;&#x2F;dave.cheney.net&#x2F;2015&#x2F;07&#x2F;02&#x2F;why-go-and-rust-are-not-competitors" rel="nofollow">http:&#x2F;&#x2F;dave.cheney.net&#x2F;2015&#x2F;07&#x2F;02&#x2F;why-go-and-rust-are-not-co...</a>