spec: remove example explaining that type B0 and B0 are identical

Every few months we get a new error report claiming that there
is a typo in the spec related to this specific example. Clearly,
the fact that two types with the same identifier are identical
seems exceedingly obvious to readers; thus the example seems not
worth the trouble. Removing it.

For #9226.
For #22202.
For #22495.
For #23096.
For #23409.

There may be more.

Change-Id: I003ba79dc460ffb028a4ecb5f29efd60f2551912
Reviewed-on: https://go-review.googlesource.com/87417
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Reviewed-by: Rob Pike <r@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Matthew Dempsky <mdempsky@google.com>
This commit is contained in:
Robert Griesemer 2018-01-11 10:41:03 -08:00
parent fe49d100e4
commit c13e0e8cee
1 changed files with 2 additions and 2 deletions

View File

@ -1,6 +1,6 @@
<!--{ <!--{
"Title": "The Go Programming Language Specification", "Title": "The Go Programming Language Specification",
"Subtitle": "Version of January 9, 2018", "Subtitle": "Version of January 11, 2018",
"Path": "/ref/spec" "Path": "/ref/spec"
}--> }-->
@ -1495,7 +1495,7 @@ A2 and struct{ a, b int }
A3 and int A3 and int
A4, func(int, float64) *[]string, and A5 A4, func(int, float64) *[]string, and A5
B0, B0, and C0 B0 and C0
[]int and []int []int and []int
struct{ a, b *T5 } and struct{ a, b *T5 } struct{ a, b *T5 } and struct{ a, b *T5 }
func(x int, y float64) *[]string, func(int, float64) (result *[]string), and A5 func(x int, y float64) *[]string, func(int, float64) (result *[]string), and A5