cppbestpractices VS concurrencpp

Turn on warnings-as-errors (-Werror or /WX). There’s a good list of recommended warnings in Jason’s book: https://github.com/cpp-best-practices/cppbestpractices

Take a look at: https://github.com/cpp-best-practices/cppbestpractices/blob/master/02-Use_the_Tools_Available.md

Collaborative Collection of C++ Best Practices. This online resource is part of Jason Turner's collection of C++ Best Practices resources. By the way, since I mentioned Jason, here's the link to his C++ Weakly channel.

This goes for C++ as well, there exist a host of off-by-default flags/features that make it a lot easier to make safe code in C++. Jason Turner's cpp best practices is a must read, using the sanitizers is another must, using facilities like g++'s _GLIBCXX_DEBUG and _GLIBCXX_DEBUG_PEDANTIC or MSVC's /GS /RTCs is a must.

Could you detail what exact tooling you are talking about ?

Like, this static analyzer looks interesting but 5 years ago clang --analyze had no trouble producing me a nice html indicating the 27 steps across 6 functions that lead to a pointer being dereferenced after being deleted. Tooling is there but it seems that pretty much no one is aware of it - see e.g. this: https://github.com/cpp-best-practices/cppbestpractices/blob/... or this: https://github.com/fffaraz/awesome-cpp for a quick look at what exists.

Also, be sure to turn on the warnings from this page (under the compilers section).*

Yep: https://github.com/cpp-best-practices/cppbestpractices/blob/master/02-Use_the_Tools_Available.md

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.