From: Russ Cox <rsc@golang.org>
Date: Mon, 16 May 2011 21:03:51 +0000 (-0400)
Subject: doc/go_mem.html: close happens before receive on closed channel
X-Git-Tag: weekly.2011-05-22~53
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=9f03d4a3f7cb5df43fdac3d726e495ae2ee4f7e4;p=gostls13.git

doc/go_mem.html: close happens before receive on closed channel

R=golang-dev, gri
CC=golang-dev
https://golang.org/cl/4551042
---

diff --git a/doc/go_mem.html b/doc/go_mem.html
index da45a07d7a..906b858e88 100644
--- a/doc/go_mem.html
+++ b/doc/go_mem.html
@@ -1,5 +1,14 @@
 <!-- The Go Memory Model -->
 
+<style>
+p.rule {
+  font-style: italic;
+}
+span.event {
+  font-style: italic;
+}
+</style>
+
 <h2>Introduction</h2>
 
 <p>
@@ -213,6 +222,17 @@ the corresponding receive on <code>c</code> completes, which happens before
 the <code>print</code>.
 </p>
 
+<p class="rule">
+The closing of a channel happens before a receive that returns a zero value
+because the channel is closed.
+</p>
+
+<p>
+In the previous example, replacing
+<code>c &lt;- 0</code> with <code>close(c)</code>
+yields a program with the same guaranteed behavior.
+</p>
+
 <p class="rule">
 A receive from an unbuffered channel happens before
 the send on that channel completes.