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

doc: update FAQ #26107

Closed
robpike opened this issue Jun 28, 2018 · 7 comments
Closed

doc: update FAQ #26107

robpike opened this issue Jun 28, 2018 · 7 comments
Labels
Documentation FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@robpike
Copy link
Contributor

robpike commented Jun 28, 2018

At the moment, just after the launch of Go 1.11 beta 1, the FAQ needs tidying. Much of the prose is about the earliest parts of the project, and the associated tone isn't right. Meanwhile, much of the modern success story is missing. As a trivial example, surely a project like Kubernetes should be mentioned, and Google's internal use is more extensive than the corresponding question implies.

The discussion of Go 2 needs updating, and so on.

I'll assign this to myself but am happy to review updates from others. I only ask we keep the answers concise; it's a FAQ, not a manual or design document.

@robpike robpike self-assigned this Jun 28, 2018
@gopherbot
Copy link

Change https://golang.org/cl/122096 mentions this issue: doc: reorganize the Go history section and mention Go 2

@robpike
Copy link
Contributor Author

robpike commented Jul 3, 2018

Please leave this one to me. I plan a major rewrite.

@ianlancetaylor ianlancetaylor added this to the Unplanned milestone Jul 11, 2018
@ianlancetaylor ianlancetaylor added the NeedsFix The path to resolution is known, but the work has not been done. label Jul 11, 2018
@gopherbot
Copy link

Change https://golang.org/cl/123496 mentions this issue: doc: update Concurrency, Functions and Methods, and Control Flow sections

gopherbot pushed a commit that referenced this issue Jul 12, 2018
…ions

Many parts of the FAQ are dusty and need cleaning up.
This is the first of a series of changes to bring it up to date.
Since it was first written at the time of release, some of the
ideas and background have changed, and some historical
remarks are largely irrelevant now.

Update #26107.

Change-Id: I1f36df7d8ecc8a1a033d5ac4fa1edeece25ed6b4
Reviewed-on: https://go-review.googlesource.com/123496
Reviewed-by: Ian Lance Taylor <iant@golang.org>
@gopherbot
Copy link

Change https://golang.org/cl/123917 mentions this issue: doc: update Implementation and Performance sections of the FAQ

@gopherbot
Copy link

Change https://golang.org/cl/123918 mentions this issue: doc: update Values, Writing Code, and Pointers and Allocation sections of the FAQ

@gopherbot
Copy link

Change https://golang.org/cl/123919 mentions this issue: doc: update Design and Types sections of the FAQ

gopherbot pushed a commit that referenced this issue Jul 15, 2018
Changes are mostly about making more about now than about the past,
changing some verb tenses, and mentioning gollvm (which should
be pronounced "gollum" if you ask me).

Update #26107

Change-Id: I6c14f42b9fc2684259d4ba8bc149d7ec9bb83d15
Reviewed-on: https://go-review.googlesource.com/123917
Reviewed-by: Ian Lance Taylor <iant@golang.org>
gopherbot pushed a commit that referenced this issue Jul 15, 2018
…s of the FAQ

Significant surgery done to the Versioning section, bringing it closer to
modern thinking.

Also add a question about constants.

Update #26107.

Change-Id: Icf70b7228503c6baaeab0b95ee3e6bee921575aa
Reviewed-on: https://go-review.googlesource.com/123918
Reviewed-by: Ian Lance Taylor <iant@golang.org>
gopherbot pushed a commit that referenced this issue Jul 15, 2018
Update #26107.

Change-Id: I8bfa5b01ce953c53f7fd7a866d0ece61ba04c618
Reviewed-on: https://go-review.googlesource.com/123919
Reviewed-by: Ian Lance Taylor <iant@golang.org>
@gopherbot
Copy link

Change https://golang.org/cl/124616 mentions this issue: doc: update the Origins section of the FAQ

@golang golang locked and limited conversation to collaborators Jul 19, 2019
@rsc rsc unassigned robpike Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

3 participants