On 04/15/2015 04:27 PM, Niall Douglas wrote:
I'm finding Chris' paper on resumable expressions instead of compiler magic created resumable functions awfully compelling:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4453.pdf
I essentially proposed the same with my functionally composed constexpr basic_future design some months ago.
Regarding that, you may be interested in a similar effort, seatar [1], with very lightweight thread-unsafe futures and continuations (future<> size is 16 bytes) with multi-core utilization provided by explicit dispatching.
Would anyone else like to comment on this library based instead of compiler based resumable execution? I'm not against some compiler support for resumable execution, but I am finding the await based proposal highly problematic, and Chris does an excellent job in summarising my own thoughts on what's wrong with it.
[1] https://github.com/cloudius-systems/seastar, see core/future.hh