On 16-10-19 02:57 AM, Oliver Kowalke wrote:
> I'm not the maintainer of boost.asio, so I don't know if an upgrade is
> planed - you might ask Christopher Kohlhoff.

This is a bit worrisome to me. We are using the Boost.Asio + Boost.Coroutine integration _extensively_ in our project.

Did the API change from Coroutine1 to Coroutine2? Is it simply a matter of including from boost/coroutine2/xxx instead of boost/coroutine/xxx based on some preprocessor macro being defined?