Re:Buffered Channels in Go: Tips and Tricks
by packetslave on Monday January 15, 2018 @03:19PM
(#16153071)
It’s trivial to implement a channel read with timeout using select and time.After(). The first N google results for “golang channel timeout” show exactly that.
[ Parent
| on HN ]
Re:Buffered Channels in Go: Tips and Tricks
by kasey_junk on Tuesday January 16, 2018 @08:56AM
(#16158143)
It’s worth noting that eliminates the range option which means you need to handle all the edge cases around closed/nil channels by hand.
On the publish side in most production cases you don’t want to use time.after as it leaks. So you’ll use either a context or a timer.
All told it’s a fair bit of boilerplate to get right everytime (which you can’t genericize) which is why I tend to use buffered channels that are sized such that being full is a degenerate case.
Re:Buffered Channels in Go: Tips and Tricks
by jnordwick on Monday January 15, 2018 @04:34PM
(#16153649)
It is still overly complex and only handles one specific timeout case. A timeout per connection? That can be a lot of extra goroutines for such a simple thing.
Or if you want a 30 second timeout since the last read? Way more complex.
Go's channels seem more than a little under developed.