Replies: 2 comments
-
We could boost::asio-ify this project, but that would break the whole "dependency free" pitch. Is it worth it? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I won't use it if it's not asio. You'll need to add so much code to make this work, that you'll be asio-lite yourself. It's pointless and a maintenance nightmare that is not worth the "dependency free" pitch. You'll be the dependency. Just support asio standalone as well, and your min dependency is a header-only library. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello.
Do you know things?
Are those things about asynchronous design?
This is where you'd write those things.
This is a discussion thread for the best practices and patterns in asynchronous design.
I don't want this project to end up in, or contribute to, callback hell.
But I also don't want to wait for senders and receivers (when's that happening, anyway?)
Beta Was this translation helpful? Give feedback.
All reactions