Keynote: How To Address 7 Major C++ Pain Points with Tools
summary
Covers concrete fixes for the top C++ pain points from the C++ Foundation survey: package management via vcpkg and Conan, shortening long builds by using an IDE to run CMake configuration (a 10‑minute build cycle becomes an instant “ready” state), CI templates and integrations, and treating CMake as a debuggable language with CMake profiling flame graphs and presets. Tooling adds editor features like macro expansion, overload navigation, and data flow analysis (DFA) that flags use‑after‑free and out‑of‑bounds; survey tooling artifacts appear in ~40% of sampled repos.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:42C++ pain points and tools
- 5:36Candies vitamins painkillers
- 8:04C++ evolution and new attempts
- 11:51Tools as painkillers
- 14:42Practical tooling benefits
- 22:35DSLs and tooling support
- 26:28C++ toolability
- 35:38Addressing pain points with tools
- 44:32Remote dev and AI assistance
- 49:14AI in modern C++
- 56:34Q&A
related talks
18mKeynote Session Preview - C++ Painkillers
18mKeynote Session Preview - C++ Painkillers
01h 32mClosing Keynote: C++ Development Tools: Past, Present and Future
53mStandard C++ Toolset
01h 01m10 Problems Large Companies Have Managing C++ Dependencies and How to Solve Them
58mC++ ecosystem: the renaissance edition
01h 28mKeynote: Safety, Security, Safety and C / C++ - C++ Evolution
54mA look at C++ through the glasses of a language tool