diff options
| author | Ian Lance Taylor <iant@golang.org> | 2013-12-12 18:48:40 -0800 |
|---|---|---|
| committer | Ian Lance Taylor <iant@golang.org> | 2013-12-12 18:48:40 -0800 |
| commit | 8189605a9681385c8464d72a13541b683fe88cdd (patch) | |
| tree | c0f5e10140f339f703170c9f8d1e365eb8bd7b44 | |
| parent | 1e6996ff2e4360db0b6f87f11688d7b23831be06 (diff) | |
| download | go-8189605a9681385c8464d72a13541b683fe88cdd.tar.xz | |
doc: change "threads" to "goroutines"
R=golang-dev, minux.ma, rsc
CC=golang-dev
https://golang.org/cl/40510049
| -rw-r--r-- | doc/go_faq.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/go_faq.html b/doc/go_faq.html index f65dff7964..e292bc879c 100644 --- a/doc/go_faq.html +++ b/doc/go_faq.html @@ -446,7 +446,7 @@ Why are map operations not defined to be atomic?</h3> <p> After long discussion it was decided that the typical use of maps did not require -safe access from multiple threads, and in those cases where it did, the map was +safe access from multiple goroutines, and in those cases where it did, the map was probably part of some larger data structure or computation that was already synchronized. Therefore requiring that all map operations grab a mutex would slow down most programs and add safety to few. This was not an easy decision, |