C++ Cryptozoology - A Compendium of Cryptic Characters
summary
Survey of quirky C++ features with concrete examples and takeaways: shows how abominable function types can be declared but not defined and why that breaks code reviews; reproduces a GCC-optimized undefined behavior example that can erase disks and recommends UB sanitizers; demonstrates template duck typing vs. concepts, the new spaceship operator auto-generating comparisons, atomic compare_exchange failing on padded unions, Unicode identifiers compiling, Voldemort (unnamable) return types, and practical advice on moved-from “zombie” states.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:17ABOMINABLE FUNCTION TYPES
- 3:35UB DEMONS
- 7:42DUCK TYPING
- 9:40FLYING SAUCERS
- 13:03TERMINATORS
- 15:23UNICORNS
- 17:26UNICORN CALL SYNTAX
- 18:19VOLDEMORT TYPES Alype that cannot be named outside of the
- 20:36ZOMBIES • What happens to an object in scope
- 23:42ZOMBIES & BRAINS
related talks
17mC++ Cryptozoology - A Compendium of Cryptic Characters
30mC++ Cryptozoology - A Compendium of Cryptic Characters :: #2
15mC++ WAT
56mCute C++ Tricks (and what you can learn from them): Part 2 of N
19mLightning Talk: Your Favorite Undefined Behavior in C++
52mNon-conforming C++: the Secrets the Committee Is Hiding From You
54mTypical C++, But Why?
52mC++ Puzzlers