C++ Core and Other C++ Guidelines - The Good, the Bad, the… Questionable?
summary
Compares C++ Core Guidelines to how teams actually apply them, showing concrete mismatches: boilerplate from blindly applying the rule of five, projects banning exceptions for legacy constraints where exceptions add 20–30 KB on tiny targets, and a codebase crippled by 1,200 Singletons across 3.5–4M lines causing tangled tests and 25‑minute test runs. Recommends automating checks with clang-tidy and clang-format, recording rationale when a rule is intentionally broken, and choosing guidelines that match team context rather than copy-pasting rules.
AI-written summary · about
chapters (9)
- 0:00C++ guidelines overview
- 4:46Rule of five impact
- 13:46Why Google bans exceptions in C++
- 19:46Single return readability
- 25:56Reference members and copyable types
- 35:32Conventional const placement
- 38:23Singleton misuse dangers
- 44:06Effective guidelines
- 54:27Q&A
related talks
50mCore and other guidelines. The good, the bad, the... questionable?
01h 29mC++ Core Guidelines - Modernize your C++ Code Base
44mCoding Guidelines – to Comply or Not Comply – Some Myth Busting
01h 08mWhat has writing about the Core Guidelines shown me?
01h 02mA Critical Look at the Coding Standards Landscape
01h 29mWriting Good C++14... By Default
59mC++ Code Smells
55mWhen C++ Style Guides Contradict