“What Do We Mean When We Say Nothing At All?”
summary
Covers concrete ways silence in C++ communicates intent: use C++17 attributes like [[fallthrough]] to mark intentional switch fallthrough, [[maybe_unused]] to avoid unused-variable warnings when asserts vanish, and [[nodiscard]] to force handling of important return values; prefer noexcept(false) over silence to show considered exception policy, mark explicit/override/const correctly, name or omit parameter names to signal use, write initializer lists and explicit returns so the absence of tokens conveys deliberate design.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:30Code as Communication
- 2:09Expressive Code
- 4:25Favorite Code Snippets
- 5:45Communicating with Nothing
- 9:30C++ 17 Attributes
- 11:58Meaningful Comments
- 14:09Default Behavior
- 16:54The 'override' Keyword
- 19:25The Use of 'Const'
- 23:03Falling out of Functions
- 25:20Loops and References
- 30:48Unnamed Parameters
- 34:02Raw Pointers
- 37:40Loops and Algorithms
- 41:51Initialization Practices
- 46:19Using New Attributes
- 47:12Summary of Intent
- 49:21Conclusion
- 50:24Q&A Session
related talks
56mWhat Do We Mean When We Say Nothing At All?
01h 37mStandard Attributes in C and C++
02mC++ Keywords Speak for Themselves
01h 28mEmbracing the **noexcept** Operator and Specifier *Safely*
07mAll the Default's Are Backwards
54mTypical C++, But Why?
01h 02mOn the benefits of non-intrusiveness
01h 01mSome Programming Myths Revisited