Boost.Asio VS build-your-own-x

Indeed looks like it, strand_executor_service.hpp is using a Mutex internally (otherwise it wouldn't make sense to me).

as a side note, Asio is also released as an independent library without the boost stuff https://think-async.com/Asio/

Now that vinniefalco is going to kill off the asio standalone (see deprecate standalone ) and only support boost what would people then recommend to switch over to.

The ASIO framework can be found at https://think-async.com/Asio/ and the relevant license for its use is included in the GitHub repository in the Vendor/licenses directory.

The library is found at https://think-async.com/Asio/.

Asio Extracted from the much bigger Boost C++ library, it's apparently a really good networking library. As a bonus it also handles async / threads. Here's a really good video tutorial by OneLoneCoder

Yes: https://github.com/chriskohlhoff/asio/blob/master/asio/include/asio/coroutine.hpp

Here's the main contributor to Asio. I looked at Asio's repository and this was the first guy.

View on GitHub

✅ codecrafters-io/build-your-own-x : https://github.com/codecrafters-io/build-your-own-x

8) Build Your Own X: Unleash your inner inventor and embark on a journey of self-creation with this collection of project ideas for building your own software, tools, and even operating systems. Fuel your entrepreneurial spirit and learn valuable engineering principles by bringing your innovative ideas to life. (https://github.com/codecrafters-io/build-your-own-x)

Also if we can someone merge this level of detail/guidance with the projects on https://codecrafters.io/, i would easily pay for something like that.

Build your own X is another useful resource for a curious mind.

This is what you're looking for: Build your own X!