On Sunday, 27 March 2016 at 15:10:46 UTC, maik klein wrote:
On Sunday, 27 March 2016 at 07:16:53 UTC, Vlad Levenfeld wrote:
https://github.com/evenex/future/
I've been having to do a lot of complicated async work lately
(sometimes multithreaded, sometimes not), and I decided to
abstract a
On Sunday, 27 March 2016 at 07:16:53 UTC, Vlad Levenfeld wrote:
https://github.com/evenex/future/
I've been having to do a lot of complicated async work lately
(sometimes multithreaded, sometimes not), and I decided to
abstract a some patterns out and unify them with a little bit
of
On Sunday, 27 March 2016 at 08:16:22 UTC, Eugene Wissner wrote:
On Sunday, 27 March 2016 at 07:16:53 UTC, Vlad Levenfeld wrote:
https://github.com/evenex/future/
I've been having to do a lot of complicated async work lately
(sometimes multithreaded, sometimes not), and I decided to
abstract
On Sunday, 27 March 2016 at 07:16:53 UTC, Vlad Levenfeld wrote:
https://github.com/evenex/future/
I've been having to do a lot of complicated async work lately
(sometimes multithreaded, sometimes not), and I decided to
abstract a some patterns out and unify them with a little bit
of
https://github.com/evenex/future/
I've been having to do a lot of complicated async work lately
(sometimes multithreaded, sometimes not), and I decided to
abstract a some patterns out and unify them with a little bit of
formalism borrowed from functional languages. I've aimed to keep
things
