Lewis Baker

CC: @GorNishanov

Note that [P1681R0](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1681r0.pdf) has a discussion of alternative ideas for allocator customisation that should be considered. @burnpanck Consider the following `task`: ```c++ template task double_it(allocator_arg_t, Allocator alloc, task t) {...

What is missing/required to make it work?

Example usage of a hypothetical `when_all_ready` implementation for this: ```c++ async_generator accept_connections(socket listeningSocket); task handle_connection(socket s); task when_all_ready(async_generator tasks); task run(socket listeningSocket) { return when_all_ready( accept_connections(std::move(listeningSocket)) | fmap(handle_connection)); } ```

> On a related note, is there any intention of making cppcoro compatible with ASIO? I don't have any current plans to add support for ASIO as far as adding...

Great questions! I'll give a brief answer here and try to write up something a bit more detailed in a document that's more easily accessible in the project. 1. The...

I'll look at splitting cppcoro up into a couple of libraries: `cppcoro.lib` and `cppcoro_io.lib`. This would include moving `io_service`, `file*` classes into `cppcoro_io.lib`, and possibly under `cppcoro::io` namespace. I'm thinking...

Within cppcoro there are two flavours of cancellation that are used with C++ coroutines. The first is the generator model. This is where a producer suspends after producing a value...

@tavi-cacina Thanks for the investigation and for the proposed patch! The `schedule_on` operator only specifies that the coroutine will _start_ execution on the specified scheduler and not that it will...

Update: MSVC still does not support symmetric transfer (at least for 2017 Update 9). I am still yet to test against 2019 builds but I have not heard that thes...