Towards Safety & Security in C++26
summary
C++26 introduces concrete safety changes: the standard reclassifies some undefined reads as erroneous behavior (so compilers must diagnose rather than exploit them), expands constant evaluation so compilers act like interpreters to catch UB at compile time, adds standard library hardening that checks preconditions and can abort on invalid accesses (tests show hardened libs stop immediately on UB), and adopts P2900 contracts with epochs and configurable violation semantics (ignore/observe/enforce).
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:50Agenda
- 3:52Security & safety
- 9:18Safety in our code, or the lack thereof
- 17:52Constant evaluation
- 24:26New features in C++26
- 33:56Options for the future
- 34:31Summary
- 35:35Outro
related talks
01h 02mTowards Correctness, Safety and Security in C++26
01h 02mTowards Safety and Security in C++26
01h 02mModern C++ Safety and Security At 20
01h 04mRemoving Needless Undefined Behavior for a Safer C++
01h 29mC++ Safety And Security Panel 2024
01h 26mA Path to Practically Safe C++
01h 28mWhat C++ Needs to be Safe
01h 26mVulnerable C++