An Introduction to Multithreading in C++20 - Anthony Williams - ACCU 2022
ฝัง
- เผยแพร่เมื่อ 25 ส.ค. 2024
- Join The ACCU Membership For Exclusive Benefits, Discounts & Reduced Conference Ticket Pricing:
accu.org/menu-...
---
An Introduction to Multithreading in C++20 - Anthony Williams - ACCU 2022
Slides & Materials: accu.digital-m...
Where do you begin when you are writing your first multithreaded program using C++20? Whether you've got an existing single-threaded application, or you're starting from scratch, C++20 provides the basic tools to help. In this talk we'll look at the C++20 facilities you should reach for first, and how to use them safely.
---
Anthony Williams
His primary area of expertise is in the development of multi-threaded applications and libraries in C++. Anthony is the author of C++ Concurrency in Action, published by Manning. He is a UK-based developer and trainer with over 20 years of experience in C++. He has been an active member of the BSI C++ Standards Panel since 2001, and is author or coauthor of many of the C++ Standards Committee papers that led up to the inclusion of the thread library in the C++11 Standard. He continues to work on new facilities to enhance the C++ concurrency toolkit, both with standards proposals, and implementations of those facilities. Anthony lives in the far west of Cornwall, England, where he currently spends most of his time developing automotive software.
---
Videos Filmed & Edited by Digital Medium: events.digital...
#accuconf #programming #multithreading
36:24
Only note is that when putting code into a slide, make some spaces and even use a smaller font to be able to use spaces.
This is a good talk about threading in C++, would recommend.
I like that he speaks about use cases and a bit theory and not just pure API calls.
Really great talk... And thank you so much. My question: because the busy wait scenario is bad, is std::barrier also optimal as std::condition_variable, when we call std::barrier::wait or std::barrier::arrive_and_wait? is std::barrier don't waste power as std::condition_variable?
Multithreading is so ugly to deploy and manage in C++ People don't write fast or lean code anymore, they use compiler flags to compile the code to be memory lean or fast; there needs to be a way to efficiently manage these requirements in the compiler.