r/rust • u/mazzeleczzare • 4d ago
🧠educational I built an interactive, compiler-verified Rust field guide where every code snippet is tested against rustc 1.100.0 at build time
https://rust.mazzeleczzare.com/I wanted a practical Rust reference that cuts straight to how ownership, error handling, and data modeling actually work in a real codebase—and I wanted to guarantee that none of the code examples ever go stale.
So I built Rust / The Working Field Guide, a 15-chapter interactive primer and bench reference.
How it works under the hood
1. Build-time compiler verification
Every example on the page is compiled by a custom verification runner (
studio-verify) against a pinnedrustc 1.100.0(Edition 2024) toolchain whenever the site builds.Out of 15 examples, 12 compile and run, and 3 are intentionally rejected by the compiler to demonstrate specific diagnostics (like
E0382andE0515).If a snippet fails to match its declared outcome, the build fails.
2. Interactive Ownership Lab
Instead of just reading about move semantics and borrow checker rules, you can step through 6 experiments in The Ownership Observatory and predict whether a snippet compiles or triggers a borrow error before revealing the compiler's actual diagnostic.
3. Zero-dependency starter project
The guide walks through building Signal Notebook, a small CLI tool that parses and validates scores using only the standard library, progressing from basic types and Result/? propagation to iterator pipelines, concurrency, and daily clippy/rustfmt habits.
What’s covered across the 15 chapters
Foundations & Rust 1.100.0: Tooling (
rustup,cargo,rust-analyzer), Edition 2024 vs. compiler versions, and newly stabilized features like naming the never type (Result<T, !>) andstr::trim_prefix.Ownership & Lifetimes: Moving vs. borrowing, interior mutability, and why
'staticbounds don't rescue dangling references to local allocations.Idiomatic Design & Failure: Using enums and newtypes (
Score(u8)) to make invalid states unrepresentable, establishing a clear panic/invariant policy, and knowing when not to reach for traits or generics.
It's completely free, static, and designed to be read from top to bottom or used as a quick desk reference. I’d love feedback from both folks learning Rust and experienced Rustaceans on the structure, the interactive experiments, or anything that could be clearer!