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

sync: inconsistent article for RWMutex #23457

Closed
mark-rushakoff opened this issue Jan 16, 2018 · 1 comment

Comments

@mark-rushakoff
Copy link
Contributor

commented Jan 16, 2018

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

Both https://golang.org/pkg/sync/ and https://tip.golang.org/pkg/sync/

What did you do?

I wasn't sure whether to write "a RWMutex" or "an RWMutex", so I Googled it.

https://www.google.com/search?q=golang+%22a+rwmutex%22
https://www.google.com/search?q=golang+%22an+rwmutex%22

What did you expect to see?

I expected to see a considerably larger number of search results for one or the other of the Google results; or, I expected to see consistent usage in the sync documentation.

What did you see instead?

I saw 268 results for "a RWMutex" and 212 results for "an RWMutex". Then I noticed the sync docs were in both search results. "A RWMutex" occurs twice in the official docs and "an RWMutex" occurs 3 times.


According to this English StackExchange post, "a" vs. "an" comes down to how the word is pronounced out loud. "Read-write mutex" is fewer syllables than "arr-double-you mutex", so I can see why it's natural to write "a RWMutex". Ultimately I would like to see one style or the other in the official docs so I don't have to think about which style to use.

@gopherbot

This comment has been minimized.

Copy link

commented Jan 16, 2018

Change https://golang.org/cl/87896 mentions this issue: sync: consistently use article "a" for RWMutex

@gopherbot gopherbot closed this in 165e752 Jan 16, 2018

@mikioh mikioh changed the title doc: inconsistent article for RWMutex sync: inconsistent article for RWMutex Jan 17, 2018

@golang golang locked and limited conversation to collaborators Jan 17, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants
You can’t perform that action at this time.