C++, like most imperative languages, have a bad tradition in writing multi-threaded applications. Concurrency safety ranks first in terms of C++ development frustration (far ahead from the second place). This talk shows how concurrent C++ applications can be designed by shifting the focus from low-level synchronisation to a set of concurrency patterns that deal with higher-level constructs.
The talk walks over a lot of examples of how one can introduce concurrency abstractions in a C++ application. As a side-effect, it shows how one can use profiling tools like Tracy to investigate concurrent behaviour.
Don’t forget to support nolocks.org by spreading the word.