(don't) Copy Paste All The Things

on YouTube ↗04m

" summary

Argument: copying a boilerplate move constructor without noexcept and without thinking about destructor behavior leads to real bugs. Example: operator move assign invokes a destructor that throws, unwinds past the intended catch, and an exception-on-construction path produces a double free when cleanup runs. The demonstrator uses a small main and catches nothing useful, reproduces heap corruption, and finds the issue with AddressSanitizer.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 0:32And I was thinking
3. 1:27Fun case #1: throwing destructor
4. 1:52Test Driver
5. 2:03And that's what happens
6. 2:37Fun case #2: exception on construction

" related talks

• 01h 02mBack to Basics: C++ Move SemanticsAndreas Fertig · CppCon 2022
• 01h 04mBack to Basics: Move SemanticsNicolai M. Josuttis · CppCon 2021
• 01h 02mBack To Basics: The Special Member FunctionsKlaus Iglberger · CppCon 2021
• 01h 06mThe Canonical ClassMichael Caisse · CppCon 2014
• 01h 01mException-Safe Code, Part IJon Kalb · CppCon 2014
• 01h 10mAn Overview of C++11/14, Part IILeor Zolman · CppCon 2014
• 01h 04mException-Safe Code, Part IIIJon Kalb · CppCon 2014
• 24mMove Constructors: Is it Possible?Miguel Young de la Sota · RustConf 2021