Learn
The course
Short lessons, a few minutes each: one idea per screen, and a question now and then to check it landed. A little Rust is enough.
How blaze works
What blaze is, and where its speed comes from.
- Lesson 1Start hereWhat blaze is, installing it, and your first build.7 steps · 3 min · 1 question
- Lesson 2What a build doesCompile, then link, and why a one-line edit can still take a while.10 steps · 4 min · 3 questions
- Lesson 3Only what changedWhy editing a function's body is cheap, and its signature less so.10 steps · 4 min · 3 questions
- Lesson 4Proc macrosWhy running them as sandboxed WebAssembly makes their output cacheable.9 steps · 3 min · 3 questions
- Lesson 5Hermetic buildsSame inputs, same output, whatever else is on the machine.8 steps · 3 min · 3 questions
- Update to lesson 5 · Oct 27NewPinned downloadsBuild scripts that download now build sealed: each download is pinned by its hash and handed in.5 steps · 2 min · 1 question
- Lesson 6Sharing workOne store for your own work, and a shared one for your team.9 steps · 3 min · 3 questions
Beyond Rust
What blaze adds to the language, its own standard library, and a compiler being proved correct. Experimental: written, and still settling.
- Lesson 7Const generic mathArithmetic on const generics, the way you always wanted to write it.6 steps · 2 min · 1 question
- Lesson 8Compile-time reflectionWrite a function once, and let it loop over any struct's fields at compile time.9 steps · 3 min · 2 questions
- Lesson 9Effects and linear typesSay what a function may do, and what a value must not be dropped without.6 steps · 2 min · 1 question
- Lesson 10bstd, its own stdA standard library where a function can touch only what it was handed.7 steps · 3 min · 2 questions
- Lesson 11Proved correctA compiler whose passes come with proofs, checked by Lean.6 steps · 2 min · 1 question
Canary and experiments
Newer, and still settling: canary releases and experimental flags.
- Update to lesson 3 · Oct 28NewWhy it rebuiltA build names every function it rebuilt and why, and blaze why tells you afterwards.4 steps · 2 min · 1 question
- Update to lesson 4 · Oct 28NewMacros that keep stateMacros that remember things between expansions now work, and the rest stay kept.5 steps · 2 min · 1 question
- Update to lesson 4 · Oct 28NewConst macrosAn experiment: a derive written as a function in your own package, expanded by blaze itself.5 steps · 2 min · 1 question
- Update to lesson 5 · Oct 28NewKept test passesA test that reads nothing from outside its code passes once, and stays passed until that code changes.5 steps · 2 min · 1 question
- Update to lesson 6 · Oct 28NewBuild scripts, sharedA build script's kept run is found from any checkout, on CI or through a remote, not just its own.4 steps · 2 min · 1 question
The end of the courseAfter lesson 11, you know how blaze builds. New updates show up in their section as blaze changes.
Your progress stays in this browser. Nothing is sent anywhere.
Credits
blaze stands on the shoulders of giants. Thank you to the people who built rust-analyzer, Cranelift, LLVM and inkwell, salsa, object, Rust, Lean and rustd (DioxusLabs), whose code or work blaze builds on. None of these projects endorses blaze. Made at ix. MIT or Apache-2.0.

