What Do We Mean When We Say Nothing At All?
summary
C++ code often uses absence of tokens to signal intent or ignorance: missing explicit vs implicit on a single-arg constructor, omitted const on methods, lack of virtual/override, or missing noexcept all change what readers infer. New attributes like [[fallthrough]], [[maybe_unused]] and [[nodiscard]] exist to mark deliberate choices. Consistent use of defaults, repeating harmless keywords (public:, return;), or short contextual comments turns accidental nothingness into an explicit design decision.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:58Writing Code is a form of Communication
- 2:33Reading Code
- 3:16Well Written Code
- 4:39Roger Orr's Favourite Code Snippet
- 7:29Let's talk about these...
- 9:03Maybe Unused, No Discard
- 11:50How Do You Disambiguate?
- 18:58Is A Raw Pointer Always A Non-owning Pointer?
- 21:07What Does & Mean? *?
- 22:13Is A Traditional for Loop Always Doing Something Odd?
- 24:15Initializing
- 31:39Communicate
- 33:12What is Not in Your Code?
- 34:27Nothingness
related talks
39mNothing is Something
44mNothing is Something
01h 02mThe Surprising Costs of void() (and Other Not-Quite-Innocuous Evils)
54mWriting C++ to Be Read
01h 28mEmbracing the **noexcept** Operator and Specifier *Safely*
01h 21mEmpirically Measuring, & Reducing, C++’s Accidental Complexity
01h 04mKeynote - What to Leave Implicit
44mUnconditional Code