Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spec: Issue with an example of Type Identities in the language spec #23096

Closed
neetle opened this issue Dec 12, 2017 · 2 comments
Closed

spec: Issue with an example of Type Identities in the language spec #23096

neetle opened this issue Dec 12, 2017 · 2 comments

Comments

@neetle
Copy link

neetle commented Dec 12, 2017

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

1.9

Does this issue reproduce with the latest release?

Yeah

What operating system and processor architecture are you using (go env)?

N/A

What did you do?

Read the Language Spec

What did you expect to see?

"A0, B0, and C0" used as an example of equivalent types in the "Type identity" section of https://golang.org/ref/spec

What did you see instead?

"B0, B0, and C0" used as an example of equivalent types in the "Type identity" section of https://golang.org/ref/spec

@neetle neetle closed this as completed Dec 12, 2017
@neetle
Copy link
Author

neetle commented Dec 12, 2017

looks like a duplicate of #22495, my bad

@mikioh mikioh changed the title Issue with an example of Type Identities in the language spec spec: Issue with an example of Type Identities in the language spec Jan 5, 2018
@gopherbot
Copy link
Contributor

Change https://golang.org/cl/87417 mentions this issue: spec: remove example explaining that type B0 and B0 are identical

gopherbot pushed a commit that referenced this issue Jan 11, 2018
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 <[email protected]>
Reviewed-by: Rob Pike <[email protected]>
Reviewed-by: Ian Lance Taylor <[email protected]>
Reviewed-by: Matthew Dempsky <[email protected]>
@golang golang locked and limited conversation to collaborators Jan 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants