Delivering Safe C++
summary
Claims that modern C++ can be written with no type violations, no resource leaks, and no memory corruption using a concrete stack of techniques: adopt safety profiles that state guarantees, apply static analysis and the C++ Core Guidelines, prefer range-checked spans and smart-pointer ownership, and enforce an ownership DAG so dangling references cannot occur. The proposed tooling mix is library-first (GSL, containers, smart pointers), analyzer-supported, and module/profile-annotated to allow gradual verified conversion and minimized runtime checks.
AI-written summary · about
related talks
01h 05mThe real problem of C++
01h 30mC++ in Constrained Environments
51m0xBADC0DE
53mFrom Chaos to Control: Overcoming C and C++’s Inherent Unsafety
01h 03mBack to Basics: The C++ Core Guidelines
54mCompile-Time Validation in C++ Programming
46mHow to write more reliable code
01h 00mException-Safe Code, Part II