The promise of static reflection in C++26: Type Traits without compiler intrinsics
summary
Claim: C++26 value-based static reflection can reproduce most standard type traits so libraries no longer need non‑portable compiler intrinsics. Evidence: a proof of concept implements many traits by reflecting types, splicing and producing aliases, and compiles against experimental compilers. Tools and comparisons: inspection of GCC/Clang/MSVC trait implementations and dependency graphs shows template churn vs shallow reflection layers. Results so far: functionality works; no hard benchmarks yet, but expected to reduce template complexity and improve maintainability when paired with a small meta header.
AI-written summary · about
chapters (6)
- 0:00Static reflection intro
- 18:00Current type traits issues
- 31:16Reflection fundamentals
- 44:39Reflection-based traits PoC
- 50:43Portable type traits future
- 54:40Q&A
related talks
01h 01mReflection
01h 08mReflections: Compile-time Introspection of Source Code
56m“Type Traits - what are they and why should I use them?"
01h 27mC++ Reflection - Back on Track
01h 10mReflection Is Good for C++ Code Health
06mReflecting Types in C++17/20
55mC++14 Reflections Without Macros, Markup nor External Tooling..
27mRe-inventing trait objects