You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in #46 (comment) the async I/O facilities provided by cppcoro should be split out into a separate library to allow applications to make use of the generic, core components of cppcoro (task, async_generator, when_all etc.) without pulling in the platform-specific async I/O subsystems.
This will allow applications to more easily use other I/O frameworks like libuv, boost::asio or the Networking TS in conjunction with cppcoro.
The text was updated successfully, but these errors were encountered:
asio already support co_awiat, can both use cppcoro and asio? i think will rewrite it use cppcoro and async asio. maybe persuade asio use cppcoro to support co_await ?
As discussed in #46 (comment) the async I/O facilities provided by cppcoro should be split out into a separate library to allow applications to make use of the generic, core components of cppcoro (
task
,async_generator
,when_all
etc.) without pulling in the platform-specific async I/O subsystems.This will allow applications to more easily use other I/O frameworks like libuv, boost::asio or the Networking TS in conjunction with cppcoro.
The text was updated successfully, but these errors were encountered: