The Tragedy of the value based architecture
summary
Value semantics collapse in large C++ apps when megabyte documents get copied everywhere and performance and threading force ad hoc mutation and locks; the actual fix is immutable, persistent data structures that give structural sharing so only changed parts are duplicated, enabling fast diffs and compact undo histories. The concrete claim: efficient persistent collections are practical in modern C++; implemented here as the Emer library using RRB trees and array-mapped tries for real-world performance.
AI-written summary · about
chapters (4)
related talks
01h 03mThe most valuable values
48mBack to Basics: Cpp Value Semantics
56mC++ Relocation - How to Achieve Blazing Fast Save and Restore and More!
01h 03mWriting sustainable software. The how and the what!
01h 01mValue Semantics: Safety, Independence, Projection, & Future of Programming
59mFunctional Programming: data
57mOo Considered Harmful
01h 03mUnlocking the value of C++20