Channel: The Pragmatic Engineer
Alice Ryhl: Rust doesn’t use exceptions
The Signal
Rust replaces traditional exception-based error handling with a value-based model, where functions return explicit results and failures are propagated via a specific operator. The creator argues this shift mandates compile-time attention to potential errors, thereby preventing the kind of unobserved runtime failures that can crash a production server.
The Case
- Rust treats errors as return values—typically through an enum-like structure—forcing developers to handle failure states rather than allowing them to propagate via silent, implicit control flow.
- The "?" operator serves as the primary propagation mechanism for keeping code concise, triggering an early return of an error if the preceding function call fails.
- The compiler enforces this safety; omitting the "?" or failing to manually handle an error result triggers a compilation error, moving potential runtime bugs earlier into the development cycle.
- While the creator asserts this system is "really easy" to use, they concede it lacks the extreme terseness of exceptions, where error handling can effectively reach zero character count at the call site.
The 1 Minute Signal Take
This is a clear, accurate explanation of why Rust’s design forces programmatic discipline at the cost of some additional syntax. Skip the video if you already understand the trade-offs between value-based error results and exceptions; it provides no extra technical depth or visual demonstration beyond the basic syntax described.
Tags
Channel: The Pragmatic Engineer