Keynote: Rust is not about memory safety
summary
Argument: Rust’s appeal is not just memory safety but that the type system and APIs make incorrect programs hard to express. Uses concrete features: Result and Option types with the question mark operator and From conversions to avoid cascade errors; enums + pattern matching replace brittle hierarchies; move semantics and the type-state pattern enforce correct lifecycles. Example: parsing an IPv4 header with the bytes crate uses try_get + ? so missing checks fail at compile time. One large refactor compiles after six hours and 300 tests with only two trivial failures, showing fewer runtime surprises.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 5:39Algebraic data types
- 9:51Error handling
- 15:54Question mark operator
- 19:26Error conversion
- 22:39Optional values
- 24:36Struct initialization
- 26:40Move semantics
- 32:28Consuming methods
- 33:53Typestate pattern
- 37:45Fearless refactoring
- 44:07Q&A
