I missed the chance to comment on github...
This also works for implementing futures and it's simple, type-safe and can
be used with select:
Of course the syntax is not as nice as built-in futures.
On Sunday, October 16, 2016 at 2:40:32 PM UTC+2, Sokolov Yura wrote:
> "future" is commonly used synchronization abstraction.
> It could be implemented in a library, using mutex, channel and interface.
> But obviously, semantically future is just a channel with buffer of
> capacity 1, but receivers do not pop
> value from a buffer, but instead every receiver receive same value. And
> "filling" future awakes all
> receivers simultaneously, similar to "closing of channel".
> So I propose to introduce "future" as a same internal type as a "channel".
> It will share representation and lot of code with buffered channel (of
> capacity 1).
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.