Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split async I/O functionality into a separate 'cppcoro_io' library #54

Open
lewissbaker opened this issue Oct 30, 2017 · 2 comments
Open

Comments

@lewissbaker
Copy link
Owner

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.

@IronsDu
Copy link

IronsDu commented Apr 1, 2019

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 ?

@IronsDu
Copy link

IronsDu commented Apr 1, 2019

Hi, i see asio can't help me translate async to sync(for co_await). so i very hope cppcoro will slit io, and focus generic, core components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants