std::jthread - I Told You Concurrency Is Tricky - Nico Josuttis [ ACCU 2021 ]

#Programming #Cpp #AccuConf
Slides: accu.org/conf-...
ACCU Website: www.accu.org
ACCU Conference Website: conference.acc...
ACCU Twitter: @ACCUConf
Streamed & Edited By Digital Medium Ltd: events.digital...
------
With C++20 we will have a new basic thread class, std::jthread.
It will fix a few flaws of std::thread, which was not designed as an easy to use RAII type and lacks the ability to support stopping a running thread.
Sounds like we only have to implement a better destructor and add a parameter to signal cancellation.
But especially with concurrency the devil is in the details.
This is not just a talk about jthread. It is a talk about how implementing even pretty simply concurrency requirements can become a tricky task with many many traps.
------
Nicolai Josuttis
Nicolai Josuttis is well known in the programming community because he not only speaks and writes with authority (being the (co-)author of the world-wide best sellers The C++ Standard Library (www.cppstdlib.com), C++ Templates (www.tmplbook.com), C++17 - The Complete Guide (www.cppstd17.com), and SOA in Practice), but is also an innovative presenter, having talked at various conferences and events. He is an independent system architect, technical manager, author, and consultant. He designs mid-sized and large software systems for the telecommunications, traffic, finance, and manufacturing industries.
------
Future Conferences:
ACCU 2022 Spring Conference, Bristol (UK), Marriott City Centre:
2022-04-05 to 2022-04-09.
-------------------------

[@treyquattro]

great presentation! Enthralling story-telling. I think Nico's next book should have the title "I Told You Concurrency Is Tricky" - straight to the top of the NY Times Bestseller List! (Alternatively, "I Told You Concurrency Is Freaky")

[@MaceUA]

Mind-blowing. But very useful! Thanks.

[@ACCUConf]

Glad you enjoyed it!

[@FreeDomSy-nk9ue]

33:35 this is powerful...
Does this also mean that future programs should always use std::jthread regardless if such a bug may or may not occur?