Breadcrumbs won't help: how not to get lost in a lambda forest
summary
Codebase uses 10,000 lambdas driving about 28,000 codecs and that scale exposes concrete failures: dangling this pointers cause crashes so never capture this; prefer shared_ptr or weak_ptr+lock or hand a lifetime token to a job queue. Excess auto hides types and can surprise return types, so use explicit types where correctness matters and auto where speed/readability tradeoffs allow. Call-stack noise from reused or recursive lambdas is real; use Visual Studio frame filtering and inject small breadcrumb state variables to locate origins.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:02Project context
- 4:20Understanding lambdas
- 9:38Lifecycle pitfalls
- 11:58Readability and performance
- 17:53Debugging challenges
- 22:32Architecture and tooling
- 26:54Q&A and discussion
