From b7ba5233550cadd2b06c4b98c702b45e7904f7ae Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Tue, 13 Nov 2018 10:23:01 -0500 Subject: [PATCH] doc/go_spec: tweak wording to avoid 'explicit assignment' misreading This text changed in CL 139099 to add "explicit" in front of "conversion". But now "explicit conversion or assignment" reads like it might mean "explicit [conversion or assignment]" when what is meant is "[explicit conversion] or assignment". To make clear that explicit does not apply to assignment, use "assignment or explicit conversion". Change-Id: I8ff7a5b3ecd9f562793502fa6808242f22264f28 Reviewed-on: https://go-review.googlesource.com/c/149340 Reviewed-by: Robert Griesemer --- doc/go_spec.html | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/go_spec.html b/doc/go_spec.html index 098a92551a..dcc81ed628 100644 --- a/doc/go_spec.html +++ b/doc/go_spec.html @@ -1,6 +1,6 @@ @@ -1348,8 +1348,9 @@ ChannelType = ( "chan" | "chan" "<-" | "<-" "chan" ) ElementType . The optional <- operator specifies the channel direction, send or receive. If no direction is given, the channel is bidirectional. -A channel may be constrained only to send or only to receive by explicit -conversion or assignment. +A channel may be constrained only to send or only to receive by +assignment or +explicit conversion. 

@@ -3624,7 +3625,7 @@ For signed integers, the operations +,
 -, *, /, and << may legally
 overflow and the resulting value exists and is deterministically defined
 by the signed integer representation, the operation, and its operands.
-Overflow does not cause a run-time panic. 
+Overflow does not cause a run-time panic.
 A compiler may not optimize code under the assumption that overflow does
 not occur. For instance, it may not assume that x < x + 1 is always true.
 

-- 
2.50.0