C++ Cryptozoology - A Compendium of Cryptic Characters :: #2
summary
Covers specific C++ oddities with concrete consequences: shows abominable function types used to forward multiple method prototypes, notes copy‑on‑write is forbidden for std::string by the standard, points out C++20 says atomic compare_exchange can fail on unions with padding bits, and recounts an undefined‑behavior example where a defaulted function pointer lets the optimizer produce code that erases a disk. Also lists phantom/Voldemort types, maximal‑munch parsing pitfalls, and the proposed unified call syntax.
AI-written summary · about
chapters (16)
- 0:00Introduction to C++ cryptic terms
- 1:03Abominable function types
- 3:09Copy-on-write strings
- 4:35Duck typing in templates
- 6:45Magical C++ features
- 7:53Maximal munch parsing
- 9:44Owlie eyes warnings
- 11:11Phantom types for safety
- 12:58Poisoning functions
- 14:07Atomic unions and padding
- 15:39Ways to terminate programs
- 18:29The void type explained
- 21:23Voldemort types
- 22:28Zombie objects after move
- 24:19Zombie names in the standard
- 25:24Bonus slides and Q&A
