From faf1e2da2d911edc717993e8edb24fe88f99b2b5 Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Sat, 14 Mar 2020 09:44:01 -0400 Subject: 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 Reviewed-by: Andrew Bonventre --- content/go-concurrency-patterns-timing-out-and.article | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content/go-concurrency-patterns-timing-out-and.article') diff --git a/content/go-concurrency-patterns-timing-out-and.article b/content/go-concurrency-patterns-timing-out-and.article index 09d2502..9bdc565 100644 --- a/content/go-concurrency-patterns-timing-out-and.article +++ b/content/go-concurrency-patterns-timing-out-and.article @@ -1,7 +1,7 @@ # Go Concurrency Patterns: Timing out, moving on 23 Sep 2010 Tags: concurrency, technical -Summary: Concurrent programming has its own idioms. A good example is timeouts. Although Go's channels do not support them directly, they are easy to implement. Say we want to receive from the channel `ch`, but want to wait at most one second for the value to arrive. We would start by creating a signalling channel and launching a goroutine that sleeps before sending on the channel: +Summary: How to implement timeouts using Go's concurrency support. Andrew Gerrand -- cgit v1.2.3