diff options
| author | Brad Fitzpatrick <bradfitz@golang.org> | 2018-04-13 19:58:08 +0000 |
|---|---|---|
| committer | Brad Fitzpatrick <bradfitz@golang.org> | 2018-04-13 20:25:50 +0000 |
| commit | 6788987eaeb886066958855e0dd2b12778204543 (patch) | |
| tree | a830ab11aad55293f6e3d294538d9332c43754c2 /content/share-memory-by-communicating.article | |
| parent | 7edc962a942e4a9d5e06dde79299f7fc5605f000 (diff) | |
content: change more links from http to https
talks.golang.org
blog.golang.org
godoc.org
swtch.com
And few misc ones done by hand.
Change-Id: Ia2c4fee630814a1ef3b143098bbac3edd6a45064
Reviewed-on: https://go-review.googlesource.com/106977
Reviewed-by: Andrew Bonventre <andybons@golang.org>
Diffstat (limited to 'content/share-memory-by-communicating.article')
| -rw-r--r-- | content/share-memory-by-communicating.article | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/share-memory-by-communicating.article b/content/share-memory-by-communicating.article index 5eaa278..2d9e77a 100644 --- a/content/share-memory-by-communicating.article +++ b/content/share-memory-by-communicating.article @@ -8,7 +8,7 @@ Andrew Gerrand Traditional threading models (commonly used when writing Java, C++, and Python programs, for example) require the programmer to communicate between threads using shared memory. Typically, shared data structures are protected by locks, and threads will contend over those locks to access the data. In some cases, this is made easier by the use of thread-safe data structures such as Python's Queue. -Go's concurrency primitives - goroutines and channels - provide an elegant and distinct means of structuring concurrent software. (These concepts have an [[http://swtch.com/~rsc/thread/][interesting history]] that begins with C. A. R. Hoare's [[http://www.usingcsp.com/][Communicating Sequential Processes]].) Instead of explicitly using locks to mediate access to shared data, Go encourages the use of channels to pass references to data between goroutines. This approach ensures that only one goroutine has access to the data at a given time. The concept is summarized in the document [[https://golang.org/doc/effective_go.html][Effective Go]] (a must-read for any Go programmer): +Go's concurrency primitives - goroutines and channels - provide an elegant and distinct means of structuring concurrent software. (These concepts have an [[https://swtch.com/~rsc/thread/][interesting history]] that begins with C. A. R. Hoare's [[http://www.usingcsp.com/][Communicating Sequential Processes]].) Instead of explicitly using locks to mediate access to shared data, Go encourages the use of channels to pass references to data between goroutines. This approach ensures that only one goroutine has access to the data at a given time. The concept is summarized in the document [[https://golang.org/doc/effective_go.html][Effective Go]] (a must-read for any Go programmer): _Do_not_communicate_by_sharing_memory;_instead,_share_memory_by_communicating._ |