osp-magnum VS concurrencpp

And I showed you that the static analyzers, which can detect several situations, are easy and straight-forward to setup and use: https://github.com/TheOpenSpaceProgram/osp-magnum/blob/master/.github/workflows/analyzers.yml

Anywhere that you are using string stream and regex would most likely be better replaced by the string_concat() function from this file https://github.com/TheOpenSpaceProgram/osp-magnum/blob/master/src/osp/string_concat.h

You can also contribute on our github under the MIT license: https://github.com/TheOpenSpaceProgram/osp-magnum

I am using concurrencpp for my project. What I like about it is that it's basically a thread pool factory with coroutines. It allows for better structuring / organizing of multithreaded work. So for me the main advantage of coroutines is that the code looks easier to follow

Equivalent concurrencpp code:

I agree. I use concurrencpp for the exact use case you described - coroutines running on simple-to-understand-executors which return some asynchronous pipe for communication.

If you look at concurrencpp, you can control exactly where and how coroutines are resumed, using executors.

concurrencpp. Modern concurrency for C++. Tasks, executors, timers and C++20 coroutines to rule them all.

Just use a good third party library like concurrencpp .

Hi, I am looking for a header-only C++14 (or lower) quality thread pool. Ideally, it would be similar to BS::thread_pool but in C++14. Most of them I find on GitHub are bloated (e.g. concurrencpp) or have many open Issues. Ideal usage would be similar to:

I use concurrencpp for my asynchronous code and the repo is written in modern cpp, with tests, sanitizers and what not.