aboutsummaryrefslogtreecommitdiff
path: root/content/go-concurrency-patterns-timing-out-and.article
diff options
context:
space:
mode:
Diffstat (limited to 'content/go-concurrency-patterns-timing-out-and.article')
-rw-r--r--content/go-concurrency-patterns-timing-out-and.article2
1 files changed, 1 insertions, 1 deletions
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