The real problem of C++
summary
Claim: modern C++ features and practices substantially eliminate common safety classes when actually used. Concrete fixes shown: rewrite nested loops with ranges to remove out‑of‑bounds assumptions (example always works and simplifies code), use consteval testing so compilers reject dereference‑null UB at compile time, adopt strong types and chrono/MP‑Units to stop accidental swaps, prefer value semantics (variant+visit) which runs ~2–3× faster than classic visitor, and aim to lift the tiny “10% bubble” so 90–98% fewer vulnerabilities materialize.
AI-written summary · about
chapters (14)
- 0:00C++ safety problem
- 2:28C++ safety problem today
- 5:17Performance vs. safety
- 7:23Bound safety in modern C++
- 10:55Undefined behavior checks
- 21:02Undefined behavior in practice
- 29:23Type safety and strong types
- 37:56Performance impact of strong types
- 41:46Lifetime safety and value semantics
- 51:13Modern C++ solutions
- 53:18Mindset and education gap
- 56:491% bubble and misinformation
- 59:16C++ teaching and books
- 1:03:07Call to action
