-
Notifications
You must be signed in to change notification settings - Fork 18k
affected/package: documentation #53771
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
Comments
@rsc let's plan it, reopen the issue and fix the docs |
We stand by the statement. Go is an opinionated language and that is our opinion. |
@ianlancetaylor, Let me try to explain how I read the advice:
Currently, every web service uses prometheus for metrics, which atomics. Unfortunately, there is indeed no reason to read the specification since there is nothing about atomics. Is it possible to change the sentence from "don't be clever" to "act on your own risk" or something like that? |
We may disagree on what the memory model document says. When I look at it, the memory model does not tell people not to read the documentation. It tells people to not write programs to rely on the details of the memory model. We're not discouraging people from reading and understanding it. Thanks for pointing out that #5045 was still open. It was fixed back in January and when the 1.19 release comes out, fairly soon, that fix will be visible on at https://go.dev/ref/mem. I closed #5045. |
Please remove
Don't be clever
advice from the memory model.The statement is annoying. I think there is no other language that has such advice in their specification.
Does this advice apply to go core team too?
The text was updated successfully, but these errors were encountered: