C++ MythBusters Strike 2
summary
Asserts that modern tooling — build profilers, Clang build analyzer and VC Perf/Windows Performance Analyzer — can cut C++ build time but project structure and header hot spots (use compiler-health to find them) usually decide results; debug builds still call std::move/std::forward unless compilers inline (Clang 16 and MSVC add intrinsics, GCC lags; -Og bypass helps); addresses sanitizer now offers address sanitizer continue-on-error for CI; warns that ranges views have reference-semantics gotchas (filter predicates can cause UB); notes real Rust ports (DirectWrite, parts of GDI) and mixed outcomes.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:28Season 1 recap
- 6:53C++ tooling importance
- 9:19Optimizing build times
- 18:06Debugging performance
- 24:36Safety versus performance
- 37:18Rust and C++ interop
- 46:06C++ future languages
- 48:33Ranges vs iterators
- 52:48CMake debugging
- 55:03Myths about new C++
- 56:29Closing and Q&A
related talks
01h 08mC++ MythBusters Strike 2
01h 44mImproving C++ Compilation Times: Tools & Techniques
01h 32mClosing Keynote: C++ Development Tools: Past, Present and Future
01h 30mTuning C++: Benchmarks, and CPUs, and Compilers! Oh My!
01h 21mC++ MythBusters
01h 27mDangerous Optimizations! in C++ - Part Deux
54mA look at C++ through the glasses of a language tool
57mThe Real Problem of C++