Modern C++
summary
Argues that “modern C++” is a historical label tied to the C++11/14/17 era rather than a living descriptor, points out the community hopes C++20 will continue that arc and mentions C++11 +14 +17 explicitly; calls out specific features like lambdas while rejecting broad rebranding as merely “functional,” jokingly proposing names such as nearly functional and urging a fresh, practical name via Twitter rather than reusing a frozen term.
AI-written summary · about
related talks
01h 01mLearning (and teaching) modern C++ - Challenges and Resources
55mNot your GrandParent’s C++
48mEarly Modern C++: How to Handle a C++03 Codebase in $CURRENT_YEAR
47mLearning (and teaching) modern C++ - Challenges and Resources
01h 31mFunctional Programming in Modern C++: The Imperatives Must Go!
01h 02mFunctional C++
59mModern C++ for Fun and Profit: This isn’t your old C++
01h 01mFunctional C++
