What's My Object?
summary
Examines making objects appear across process boundaries and shows why std::variant and C-style discriminated unions fail: huge autogenerated headers, bloated memory because unions size to the largest message, and surprising compile-time blowup when files hit millions of lines. Demonstrates that P0593 lets code treat bytes-as-objects safely for trivially copyable types, explains the missing library piece start_lifetime_as, and reports that with those constraints the byte-buffer header parsing approach works without undefined behavior.
AI-written summary · about
chapters (5)
related talks
01h 04mUndefined Behavior in the STL
44mDebugging memory corruptions in C++
33mUndefined Behavior in C++: What Every Programmer Should Know and Fear
01h 06mSecurity Beyond Memory Safety - Using Modern C++ to Avoid Vulnerabilities by Design
01h 02mBack To Basics: Undefined Behavior
01h 04mRemoving Needless Undefined Behavior for a Safer C++
01h 27mDangerous Optimizations! in C++ - Part Deux
48mSecure C++ Programming