On Thursday, 18 July 2013 at 18:38:57 UTC, Matt wrote:
On Thursday, 18 July 2013 at 17:55:36 UTC, Sean Kelly wrote:
Not as such. I'd like to make Fibers each have their own
message queue in std.concurrency, but that means making TLS
work at the fiber level, which is tricky.
I think there is value in the CSP model (ie. channels), but
haven't done anything about it in terms of library work.
From what I've read about Fibers, it seems they are more
similar to what I'm looking for (a post on stackoverflow
implied they are similar to Erlang's implementation of
lightweight tasks). Does this mean to say they are similar to
the tasks provided by std.parallelism?
Thanks for the reply,
Matt.
vibe.d is based on fibers, you might want to check it out.
http://vibed.org/features#fibers
