From 8189605a9681385c8464d72a13541b683fe88cdd Mon Sep 17 00:00:00 2001 From: Ian Lance Taylor Date: Thu, 12 Dec 2013 18:48:40 -0800 Subject: [PATCH] doc: change "threads" to "goroutines" R=golang-dev, minux.ma, rsc CC=golang-dev https://golang.org/cl/40510049 --- doc/go_faq.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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?

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, -- 2.48.1