We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Context: https://tour.golang.org/concurrency/5
It would be very useful to have a "Would you like to know more?" link in the description to the documentation, in this case https://golang.org/ref/spec#Select_statements
The text was updated successfully, but these errors were encountered:
@campoy?
Sorry, something went wrong.
This might end up making us add links to the specs on every single page of the tour.
We already point to the specs at the end of the tour (http://tour.golang.org/concurrency/11)
What do you think, @adg?
I think it doesn't hurt to add more links. Probably we should be adding more links to definitions and resources throughout the tour.
I'll rename this issue to track the general issue of adding such links.
Here's an attempt at policy:
Some links to Effective Go would be also nice. Learned many things in Effective Go the hard way.
No branches or pull requests
Context: https://tour.golang.org/concurrency/5
It would be very useful to have a "Would you like to know more?" link in the description to the documentation, in this case https://golang.org/ref/spec#Select_statements
The text was updated successfully, but these errors were encountered: