The Rust Book,
for orchestrators.
Twenty chapters. Every concept of the classic Rust Book, retold for the builder whose agents write most of the code. Real snippets from the Sail query engine ground every chapter.
Contents
20 chapters · ~4 hours of reading- 018 minGetting startedWhy Rust matters now, and how to set up.
- 0210 minThe guessing gameWriting a real program in twenty minutes.
- 0314 minCommon conceptsVariables, types, functions, flow.
- 0418 minOwnershipThe feature Rust is famous for.
- 0512 minStructsNaming the parts of a thing.
- 0612 minEnums and matchingClosed sets and exhaustive dispatch.
- 0710 minPackages, crates, modulesHow a Rust project is organized.
- 0812 minCommon collectionsVec, String, HashMap, and friends.
- 0914 minError handlingThe part that catches half the bugs.
- 1018 minGenerics, traits, lifetimesThe three things that scale Rust.
- 1112 minTestingBuilt-in tools, no framework wars.
- 1216 minI/O projectBuild a real CLI, end to end.
- 1312 minIterators and closuresFunctional features that earn their keep.
- 1410 minMore about CargoProfiles, workspaces, publishing.
- 1514 minSmart pointersBox, Rc, Arc, RefCell, Mutex.
- 1614 minFearless concurrencyThreads, channels, Send and Sync.
- 1710 minOOP featuresWhat Rust gives you, and what it does not.
- 1812 minPatterns and matchingDestructure everything.
- 1916 minAdvanced featuresUnsafe, macros, advanced traits.
- 2018 minFinal projectA multithreaded web server, by hand.
The Rust Book is excellent. It assumes you will write most of your Rust by hand. Many builders today do not. This edition keeps every concept and reframes each one around the orchestrator's job: reading, gating, and steering agent-written Rust.
Every chapter that fits draws a Sail-aside box with a real snippet from the Sail query engine: a production Rust codebase you can read, fork, and learn from on Apache 2.0 terms.
For the operational side, read the Orchestrator track: 12 failure modes, the cargo gates, prompting templates, and a 5-minute PR review playbook. The book teaches the language; the playbook teaches the workflow.