mysql VS binary_io

Documentation: https://anarthal.github.io/mysql/index.html

For example Boost-Beast and Boost-Mysql(not officially boost) receive user provided asio::io_context and every other library in this ecosystem should be the same.

Boost.MySQL has just started review process for acceptance of boost. It's based on asio. https://github.com/anarthal/mysql

The library is at https://github.com/anarthal/mysql and the documentation is at https://anarthal.github.io/mysql/. Examples under https://anarthal.github.io/mysql/mysql/examples.html.

I wrote a modern iostreams library a while back that was born out of these exact same frustrations: https://github.com/Ryan-rsm-McKenzie/binary_io

I wrote a library called binary_io, specifically for handling bespoke binary formats

I feel like standard C++ streams are terribly clunky to use, and suck at anything that isn't reading a plain text file encoded in ASCII. So when I saw Modern std::byte stream IO for C++, I got excited that C++ might finally get some powerful abstractions for IO that weren't agonizingly painful to customize/use. However, sadly the author abandoned the paper (and also their github/reddit account). So I went ahead and wrote my own library which was loosely based off of that paper, and uses C++20. The result is a set of generic streams which can be used to implement a binary IO protocol for a wide variety of sources, and which can easily be extended for other sources as well (have you ever tried to write your own std::basic_streambuf?). It's aptly named binary_io.