On Fri, Aug 18, 2017 at 12:02 PM, John Souvestre <j...@souvestre.com> wrote: > > I think that both of the suggestions below are great. But I’m left > wondering about the Go mantra > > > > Do not communicate by sharing memory. Instead, share memory by > communicating. > > > > What does it say? It starts off with communicating as the goal, but doesn’t > tell you how to do it. Then sharing memory is the goal and the solution it > provides (communicating) is only right some of the time. > > > > Am I missing something? Should this be replaced?
As I see it, the point of the proverb is to focus on having goroutines use explicit communication mechanisms, such as channels and mutexes, to hand control of an area of memory over to another goroutine. An example of communicating by sharing memory would having one goroutine poll a memory location that is then changed by a different goroutine. As a general guideline, prefer explicit communication mechanisms. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
