Tools from the C++ Ecosystem to save a leg
summary
Claims that tools can prevent C++ footguns get demonstrated with concrete tooling and limits: clang-tidy modernize applies automated migrations and clang-tidy totals ~200 checks; cppcheck offers long‑running basic checks; dynamic tools trade speed for convenience — AddressSanitizer/UBSan run ~2–5× slowdown while Valgrind runs ~20–50×; refactorings often only work per translation unit so project‑wide renames fail; package managers like conan and Hunter exist; metaclass code generation lacks IDE preview so generated output is unseen until compile.
AI-written summary · about
chapters (39)
- 0:00Introduction
- 1:30Yarn quote
- 2:36C heritage
- 6:02Bust test
- 7:08Goto fail
- 9:00Visible types
- 9:56Macros
- 11:01Code Quality
- 13:10Tools
- 16:43Style guides
- 17:59reformat
- 19:01clonk
- 21:18IDs
- 22:15Extract Style
- 24:09Code Generation
- 27:05Matic Classes
- 30:49CPP Check
- 32:03Clunk Analyzer
- 34:35C Score Guidelines
- 35:46Coverity
- 37:17Other tools
- 37:55Data flow analysis
- 38:54Dynamic code analysis
- 39:12Valgrind vs sanitizers
- 41:35Valgrind
- 43:34Cache Profiler
- 44:51Address Sanitizer
- 45:24Fret Sanitizer
- 46:13undefined behavior sanitizer
- 46:59dataflow sanitizer
- 47:34refactoring
- 48:44requirements
- 49:56refactorings
- 51:04unit testing
- 53:24package managers
- 55:21variety of build system
- 57:36Conan
- 58:24Resources
- 58:46Questions
related talks
52m“Tools from the C++ eco-system to save a leg”
55mStandard C++ Toolset
01h 32mClosing Keynote: C++ Development Tools: Past, Present and Future
01h 05mImprove your code with Clang Tooling
01h 01mBetter Tools in Your Clang Toolbox
48mTooling Intuition
01h 03mHow to Build Your First C++ Automated Refactoring Tool
29m“The Current State of (free) Static Analysis"