The Philosophy of Google's C++ Code
summary
Google documents why specific rules exist and what actually changed: the codebase spans 100 million lines of code, an indexer called kaith lets maintainers find uses across it, and formatting is automated so teams should use clang format. Rules that matter are concrete like no exceptions and no non-const references and using unique_ptr to show ownership transfer. Some old rules get dropped when they cost more than they buy as in removing the streams ban, and the practices demonstrably reduce surprises and maintenance load.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:50BORING QUESTION!
- 3:05WRONG QUESTION!
- 10:56Philosophies of the Style Guide
- 32:42Have a style guide. Tailor it to your situation.
- 33:33Use your guide to encourage "good" and discourage "bad."
- 34:53Questions?
related talks
01h 03mBack to Basics: The C++ Core Guidelines
13mKeep your code sane with clang-tidy
01h 30m50 shades of C++
01h 03mLearning and teaching modern C++
01h 49mKeynote: What C++ is and what it will become
01h 03mUnlocking the value of C++20
01h 01mThe Future of C++ Parallel and Concurrency Safety Guidelines
53mFrom Chaos to Control: Overcoming C and C++’s Inherent Unsafety