CppCon 2019: Rainer Grimm “Atomics, Locks, and Tasks (part 1 of 2)”

—
—
—
The history of concurrent programming in C++ is short. It began in 2011. At first peek, C++11, and later C++-standards support only the abstractions for library developers but not for application developers.
But the second view gives more details. Using the right techniques and the right abstraction make it possible to use the concurrent features safely.

This class shows you the safe way:

- How you can use atomics for simple jobs.
- How locks help to master shared state without the inherent danger of mutexes.
- How tasks are a significant improvement to threads and are part of the future and not of the past. Tasks allow you to
* share state without the need of synchronisation.
* manage values, notifications, and exceptions in a concurrent environment.
* create producer/consumer workflows without the highly error-prone condition variables.
- How to use concurrency in a declarative style with the parallel STL.
—
Rainer Grimm
Trainer, Modernes c++
—

*-----*
*-----*

[niklasleh]

The person that asked the question was absolutely right. The two constructed unique locks are just useless?