Learn

Start here

Rust, rebuilt in milliseconds

blaze build builds Rust. Edits rebuild in milliseconds.

A short course, one idea per screen. Press Continue or →.

Why it is fast

rustc is incremental, but cargo still starts one per affected crate, each reloading its saved state, then links everything again.

blaze keeps your workspace in memory and redoes only the functions you changed.

Install it

curl -fsSL https://ix.dev/blaze | sh

macOS on Apple silicon or Linux. No Rust needed: blaze brings its own. Details: Install.

Your first build

blaze run

The first build loads everything into a background daemon. After that, each save rebuilds one piece:

Finished `dev` profile [blaze] target(s) in 0.02s

Check

Why is the second blaze run so much faster?

  1. It downloaded a prebuilt copy.Nothing is downloaded: your code is compiled on your machine.
  2. The daemon kept everything in memory and redid only the edit.Right: load once, then only what changed.
  3. It skipped type checking.Types are checked on every build.
Show the answer

The daemon kept everything in memory and redid only the edit. Right: load once, then only what changed.

The commands

blaze build run test check benchcargo's commands and flags
blaze statuswhat the daemon holds
blaze stopsave its state and stop

Rebuild on save with any watcher: watchexec -e rs -- blaze build.

Next

Next: how blaze gets its speed, then what it adds to Rust: const generic math, effects, its own std, and proofs in Lean.

All lessons: the course map.