Almost Always Avoiding auto
summary
Claims that using auto everywhere causes debugging pain and surprising types, demonstrates with real debugging scenarios: chasing excessive return-value chains across 20 files in a GDB session, hitting unexpected unsigned widths, and confusing pointer and qualifier intent. Shows concrete language behavior: auto removes top-level const/volatile and template deduction surprises, contrasts the one true use (naming lambdas) with cases where an explicit int or pointer would have been shorter and clearer.
AI-written summary · about
related talks
01h 02mEmbracing Trailing Return Types and `auto` Return SAFELY in Modern C++
36mBreadcrumbs won't help: how not to get lost in a lambda forest
36mThe language that isn't
01h 01mBack to Basics: Debugging in C++
01h 03mHidden Overhead of a Function API
01h 30m50 shades of C++
01h 05mThe real problem of C++
33mC++: Unexpected Behaviour