From 9f71ed226f64acc4635b617d56ede2305155fb5a Mon Sep 17 00:00:00 2001 From: Igor Tonkopryadchenko Date: Fri, 17 May 2019 08:11:39 +0300 Subject: [PATCH] Add more words to the quote from the actual Go documentation, it actually has an opposite meaning --- src/ch16-03-shared-state.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/ch16-03-shared-state.md b/src/ch16-03-shared-state.md index e5491d147c..7050d4db15 100644 --- a/src/ch16-03-shared-state.md +++ b/src/ch16-03-shared-state.md @@ -2,7 +2,7 @@ Message passing is a fine way of handling concurrency, but it’s not the only one. Consider this part of the slogan from the Go language documentation again: -“communicate by sharing memory.” +“do not communicate by sharing memory.” What would communicating by sharing memory look like? In addition, why would message-passing enthusiasts not use it and do the opposite instead?