The Rust That Could Have Been
summary
A history of specific design experiments and why they fail or survive: typestate implemented as predicates as opaque Rust functions that mostly force runtime checks and little static proof, structural records and objects that require heap allocation vtables and implicit GC which clash with trait coherence, a working but disastrously slow segmented stacks causing benchmark slowdown and complexity calling C, and an optional GC replaced by reference counting plus cycle handling; what survives is ownership, traits, and the goal of dropping heavy runtimes.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 4:00The Visions
- 4:33Type State
- 8:22Predicates
- 11:42Structural Typing
- 12:35Struct Type
- 13:44Object Type
- 15:27polymorphism
- 19:07operating systems
- 20:52allocating the step
- 27:32conclusion
- 27:51Questions
related talks
35mLet’s Talk About Rust
49mThe Eternal Sunshine of the Spotless Programming Language
46mKeynote: Rust is not about memory safety
19mRust Without Tears: A Guide to Avoiding Common Traps
44mTyped Design Patterns for the Functional Era
26mThe Freedom of Static Typing
40mRust’s approach of getting things right
58mRust for The Curious C++ Developers