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

Typo in Go memory model doc #16440

Closed
FZambia opened this issue Jul 20, 2016 · 2 comments
Closed

Typo in Go memory model doc #16440

FZambia opened this issue Jul 20, 2016 · 2 comments
Labels
Documentation Issues describing a change to documentation. FrozenDueToAge
Milestone

Comments

@FZambia
Copy link

FZambia commented Jul 20, 2016

Hello, looks like there is a typo in docs – in Go memory model document the word serialize used instead of synchronize in 2 places: first line and second

@ianlancetaylor
Copy link
Member

It's not obvious to me that "serialize" is wrong here. Rob wrote it so I'll let him decide.

@ianlancetaylor ianlancetaylor added the Documentation Issues describing a change to documentation. label Jul 20, 2016
@ianlancetaylor ianlancetaylor added this to the Go1.8 milestone Jul 20, 2016
@robpike
Copy link
Contributor

robpike commented Jul 20, 2016

It is correct as written. Serializing memory access is well-defined, and means that accesses occur in a sequence rather than simultaneously. It is difference from synchronization, which can mean exactly the opposite in practice. Think of the phrase 'synchronize your watches': you're guaranteeing simultaneity then.

Serialize is correct and unambiguous.

@robpike robpike closed this as completed Jul 20, 2016
@golang golang locked and limited conversation to collaborators Jul 20, 2017
@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 Issues describing a change to documentation. FrozenDueToAge
Projects
None yet
Development

No branches or pull requests

4 participants