Vinnie Falco

I'm having a hard time understanding this code. It looks like you duplicated a significant amount of functionality of the `asio::ip::tcp::basic_acceptor`. Why did you do that? It seems to me...

What is a `DatagramSocketType`? My point is that you have this `dtls::acceptor` class which seems to duplicate a lot of functionality of `basic_acceptor`. You are calling `get_implementation` on the socket?...

This topic seems mighty familiar :)

This is just a guess but I think you need to be using the Asio coroutines, not the Coroutines TS ones, otherwise you lose the guarantees that your I/O objects...

Side note, I have rewritten a lot of Beast's composed operations to use stackless coroutines. They are a little weird but damn useful. And their performance characteristics are outstanding, you...

>I thought that given the Universal Async Model, one could write the appropriate Awaiter and associated invoke hooks etc to get things to work. They still have to run on...

>async_connect doesn't work either Of course it does. **ConnectHandler** signature is `void(error_code)`. http://www.boost.org/doc/libs/1_65_0/doc/html/boost_asio/reference/ConnectHandler.html You can use this signature for your completion handler: ``` void op::operator()( boost::system::error_code ec = {}, std::size_t...

>Anyway, I'm not convinced coroutines is best for what we want but it might enable me to make progress as I've stalled for weeks trying to solve the pipeline problem....

>P0286r0 Beautiful :) However, @akoolenbourke before you get too excited note that none of the examples in P0286r0 demonstrate the implementation of initiating functions using `co_await`.

> Also, I wouldn't use coroutines in a composed operation. I'd use them in client code. You wrote: >We want to build a set of networking building blocks, a level...