Back to Basics: The C++ Core Guidelines
summary
Claims that the Core Guidelines boil down to concrete rules for interfaces, functions, classes, concurrency and templates and lists 350 rules (roughly 600–700 pages). Recommends explicit constructors, RAII, rule-of-zero/ six, prefer strong types, enum class, move semantics, std::vector/array, and smart pointers to model ownership because pointers broken by design. Demonstrates a real data race and shows detection with -fsanitize=thread (sanitizers in GCC/Clang), and notes the Guideline Support Library for automated checks.
AI-written summary · about
chapters (28)
- 0:00C++ Core Guidelines intro
- 1:49Why C++ Core Guidelines matter
- 5:24Guidelines structure and challenges
- 7:14Designing safe interfaces
- 8:36Parameter passing in C++
- 11:11Ownership with pointers
- 13:24Transferring ownership
- 15:10Structs vs classes
- 16:57Regular types and rule of six
- 19:05Defaulting special members
- 21:54Explicit constructors
- 22:17Destructors necessity
- 23:42Base class destructors
- 33:06Scoped enums in C++11
- 35:29RAII idioms
- 38:00Good naming in C++
- 39:28Avoid unsigned arithmetic
- 41:17Performance optimization
- 43:46Measuring bottlenecks
- 44:30Move semantics and constexpr
- 45:54Concurrency with std::jthread
- 50:17Threading issues with sanitizers
- 53:23Error handling
- 54:25When to use templates
- 55:50Template deduction and constraints
- 56:32Array vs vector vs string
- 57:37Final thoughts and resources
- 1:00:13Q&A on C++20 spaceship
related talks
39mBack to Basics: The Rule of Five in C++
01h 40mBack to the Basics! Essentials of Modern C++ Style
01h 01mThe Future of C++ Parallel and Concurrency Safety Guidelines
01h 03mLearning and teaching modern C++
01h 30m50 shades of C++
01h 29mDelivering Safe C++
01h 05mBack To Basics: Overload Resolution
59mBack to Basics: Generic Programming in C++