From: Robert Griesemer <gri@golang.org>
Date: Fri, 31 May 2013 18:21:37 +0000 (-0700)
Subject: spec: better wording re: receiving from closed channels
X-Git-Tag: go1.2rc2~1368
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=ab5c762a4644c5701dfa14905802979b04cee4b0;p=gostls13.git

spec: better wording re: receiving from closed channels

As suggested by ej@evanjones.ca.

Fixes #5604.

R=r
CC=golang-dev
https://golang.org/cl/9899043
---

diff --git a/doc/go_spec.html b/doc/go_spec.html
index b3134eed83..09bbb85f68 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -1,6 +1,6 @@
 <!--{
 	"Title": "The Go Programming Language Specification",
-	"Subtitle": "Version of May 20, 2013",
+	"Subtitle": "Version of May 31, 2013",
 	"Path": "/ref/spec"
 }-->
 
@@ -3301,9 +3301,8 @@ from the channel <code>ch</code>. The channel direction must permit receive oper
 and the type of the receive operation is the element type of the channel.
 The expression blocks until a value is available.
 Receiving from a <code>nil</code> channel blocks forever.
-Receiving from a <a href="#Close">closed</a> channel always succeeds,
-immediately returning the element type's <a href="#The_zero_value">zero
-value</a>.
+A receive operation on a <a href="#Close">closed</a> channel can always proceed
+immediately, yielding the element type's <a href="#The_zero_value">zero value</a>.
 </p>
 
 <pre>