Re: [boost] boost::coroutines and boost::asio

atkinson julian wrote:

Hi, the combination of asio and coroutines would seem to represent a little bit of magic (layering a linear code model over an async event framework and without the attendant issues involved in multithreading).

Yes, it would be pretty cool. However, couldn't the syntax be directly that of blocking asio calls? coro::future<error_type, iterator_type> future(self); resolver.async_resolve(query, coro::make_callback(future)); coro::wait(future); is really the same thing as tuple<error_type, iterator_type> result = resolver.resolve(query);