4 ms·
> design it right using channels, constructs like Futures and Promises aren't necessary Careful implying that using futures and promises are incorrect unless y
by codygman 12y ago
> design it right using channels, constructs like Futures and Promises aren't necessary
Careful implying that using futures and promises are incorrect unless you can prove that channels can do anything futures and promises can do while doing it better.
Do you have any examples?
- Zikes 12y agoIn Go they are incorrect at worst, not idiomatic at best. That's due to the nature of the language as channels are built-in primitives capable of fulfilling the roles of either, not a slight on the efficacy of the constructs themselves. http://golang.org/doc/effective_go.html#channels http://golang.org/doc/effective_go.html#channels