From: Russ Cox <rsc@golang.org>
Date: Mon, 5 Dec 2011 19:22:23 +0000 (-0500)
Subject: spec: remove contentious composite literal shortening
X-Git-Tag: weekly.2011-12-06~25
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=98553f1422392f135989e0daafab352b66c561c2;p=gostls13.git

spec: remove contentious composite literal shortening

R=gri, r, gustavo, r
CC=golang-dev
https://golang.org/cl/5451099
---

diff --git a/doc/go_spec.html b/doc/go_spec.html
index 04cab1dbb6..cded51a4a7 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -1,5 +1,5 @@
 <!-- title The Go Programming Language Specification -->
-<!-- subtitle Version of December 2, 2011 -->
+<!-- subtitle Version of December 5, 2011 -->
 
 <!--
 TODO
@@ -2120,8 +2120,6 @@ elements that are themselves composite literals may elide the respective
 literal type if it is identical to the element type of <code>T</code>.
 Similarly, elements that are addresses of composite literals may elide
 the <code>&T</code> when the the element type is <code>*T</code>.
-The same elisions may be applied to field values within a struct literal,
-but only if the value has a field name key.
 </p>
 
 
@@ -2131,13 +2129,6 @@ but only if the value has a field name key.
 [][]int{{1, 2, 3}, {4, 5}}        // same as [][]int{[]int{1, 2, 3}, []int{4, 5}}
 
 [...]*Point{{1.5, -3.5}, {0, 0}}  // same as [...]*Point{&Point{1.5, -3.5}, &Point{0, 0}}
-
-type List struct {
-	Val int
-	Next *List
-}
-
-&List{Val: 1, Next: {Val: 2}}     // same as &List{Val: 1, Next: &List{Val: 2}}
 </pre>
 
 <p>