diff options
| author | Russ Cox <rsc@golang.org> | 2020-03-14 09:44:01 -0400 |
|---|---|---|
| committer | Russ Cox <rsc@golang.org> | 2020-03-17 20:58:41 +0000 |
| commit | faf1e2da2d911edc717993e8edb24fe88f99b2b5 (patch) | |
| tree | 3b7d10f5f95b7bc9ca63d0591bd120b8d8f015b6 /content/share-memory-by-communicating.article | |
| parent | af5018f64e406aaa646dae066f28de57321ea5ce (diff) | |
content: write real summary for each article
The pre-Markdown blog invented a summary by copying
the first paragraph of text. Often this was nonsense or
at least useless.
The new Markdown-enabled present format adds an
explicit Summary line. The conversion populated these
with the same first paragraph that the old format would
have used implicitly.
This commit rewrites them all to be proper short summaries.
Change-Id: If2e1e101b95558d7ecd53c613f733a7f89c680f1
Reviewed-on: https://go-review.googlesource.com/c/blog/+/223598
Run-TryBot: Russ Cox <rsc@golang.org>
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 12bff79..c254ea0 100644 --- a/content/share-memory-by-communicating.article +++ b/content/share-memory-by-communicating.article @@ -1,7 +1,7 @@ # Share Memory By Communicating 13 Jul 2010 Tags: concurrency, technical -Summary: 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. +Summary: A preview of the new Go codelab, Share Memory by Communicating. Andrew Gerrand |