Lightning Talk: Thread Safety With synchronized_value in C++
summary
Proposes a concrete library type that wraps data and provides automatic locking so adding thread safety to legacy code avoids invasive edits. Demonstrates a wrapper called synchronized_value that exposes an operator-> to call container methods while taking locks, and a sibling update_guard to hold exclusive access without constant lock/unlock. Claims reduced boilerplate versus manual mutex fields and delegation, shows an example implementation URL but notes the local repo commit failed before the talk.
AI-written summary · about
related talks
59mThreads and Locks must Go
01h 07mAn Introduction to Multithreading in C++20
05mLightning Talk: Rust Without ‘Unsafe’ Is as Unsafe as C++
01h 04m[old version]The C++20 Synchrononization Library
01h 00mLock-Free Programming (or, Juggling Razor Blades), Part I
04mLightning Talk: Modernizing SFML in Cpp
52mBest Practices for Concurrency
11mLightning talk: ArcShift: Going faster than RwLock