The next big Thing
summary
Claim: design by introspection is the practical next big thing because it combines compile‑time queries, does this code compile?, and arbitrary compile‑time processing to adapt libraries instead of forcing rigid policies. Evidence: allocators implemented with introspection drop 45k→12k lines in one language; a checked‑integer prototype compresses doc+tests+code into a single ~3k‑line file and matches hand‑written speed. Problems: C++’s current static_if gives the wrong scope semantics and output generation is missing, so the three required primitives (input introspection, Turing‑complete compile‑time processing, and code‑generation-as-strings) must land for this to scale.
AI-written summary · about
chapters (11)
- 0:00Introduction and anecdotes
- 4:07Future predictions
- 10:51The problem of code size
- 15:07Concepts vs. Introspection
- 23:07Design by introspection
- 34:33Implementation requirements
- 39:42Optional interfaces
- 45:20Criticizing if constexpr
- 55:58Checked integers example
- 1:08:03Architecture and design
- 1:18:24Q&A session
related talks
02h 02mPeering forward: C++'s next decade
01h 37mPeering Forward - C++’s Next Decade
01h 03mC++ Reflection: Back on Track
40mReflection in C++ Next
59mConcepts driven design
36mThe language that isn't
01h 02mRust/C++ Interop: Carcinization or Intelligent Design?
01h 05mC++ Reflection Based Libraries to Look Forward To