Re:Notes on structured concurrency, or: Go statement conside...
by atrn on Wednesday April 25, 2018 @08:55PM
(#16927928)
Coming from an occam/transputer background (in the 1980s) I felt goroutines were too low level. Luckily its trivial to add a PAR-like construct via sync.WaitGroup (e.g. github.com/atrn/par). That said Go's channels are far easier to work with - buffering and multi-producer/-consumers being very common needs which, in occam, you implement yourself. The lack of guards in Go's ALT (select) is a shame and the nil channel hack is just that, a hack.
[ Parent
| on HN ]
There are no comments on this comment yet.