qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-21 10:24:39 -07:00
Code Releases Activity

spec: remove contentious composite literal shortening

Browse Source 
R=gri, r, gustavo, r
CC=golang-dev
https://golang.org/cl/5451099
This commit is contained in:
Russ Cox 2011-12-05 14:22:23 -05:00
parent abc7df9686
commit 98553f1422
1 changed files with 1 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/go_spec.html
View File

@ -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>