Repolode
Submit
indexable-inc

indexable-inc/blaze

A drop-in cargo front end that makes incremental Rust rebuilds take milliseconds by JIT-compiling only changed functions into the running program.

View on GitHubWebsite
Stars
2,034
Forks
72
Open issues
115
Last commit
13 hours ago

What is it?

blaze runs alongside cargo and keeps your project compiled in memory. The same commands work with a `blaze` prefix, such as `blaze build`, `blaze run`, and `blaze test`, and any other cargo command passes straight through to cargo.

After an edit, blaze compiles only the functions you changed and writes them into the program cargo already built, instead of relinking the whole binary. Programs that opt in can pick up the new code while they keep running. The project's benchmarks report edit-and-build times that are several times faster than cargo on the projects tested, including ripgrep, helix, and bun.

blaze supports macOS on Apple silicon and Linux; on Windows, builds fall back to cargo. It uses its own Rust toolchain, which can differ from the project's pinned version, and it uses noticeably more memory, so cargo check or CI should remain the final check.

Key features

  • 01Uses the same commands as cargo with a blaze prefix.
  • 02Recompiles only changed functions and patches them into the existing program.
  • 03Supports live edits in running programs that opt in.
  • 04Passes other cargo commands through unchanged.

Use cases

  • Speeding up the edit-build-run loop on a large Rust project.
  • Iterating quickly on a Rust application or game with live code changes.
  • Reducing wait times for local test runs during development.

Quick start

  1. 1

    Run the official install script from the README

  2. 2

    In any Rust project, run blaze in place of cargo run

    blaze run

Things to know

  • Supported only on macOS (Apple silicon) and Linux; on Windows every build falls back to cargo.
  • blaze uses its own bundled nightly Rust toolchain, not the project's pinned toolchain.
  • It trades memory for speed and can use a few GB for a small project.
  • The project is young, so cargo check or CI should remain the final check.

Featured in Repolode Weekly

In collections

Compilers, transpilers & programming languages

Topics

#rust#cargo#incremental-compilation#jit#compiler#developer-tools#hot-reload#cranelift#live-coding#rust-analyzer

FAQ

What is blaze?
A drop-in cargo front end that makes incremental Rust rebuilds take milliseconds by JIT-compiling only changed functions into the running program. blaze runs alongside cargo and keeps your project compiled in memory. The same commands work with a `blaze` prefix, such as `blaze build`, `blaze run`, and `blaze test`, and any other cargo command passes straight through to cargo.
Is blaze free to use? What license does it have?
blaze is open source under the Apache-2.0 license. Check the license terms before using it in commercial products.
Is blaze still maintained?
Actively maintained. The last commit to blaze was on Nov 6, 2026.
What can I use blaze for?
Speeding up the edit-build-run loop on a large Rust project. Iterating quickly on a Rust application or game with live code changes. Reducing wait times for local test runs during development.
How do I install blaze?
Run the official install script from the README In any Rust project, run blaze in place of cargo run: blaze run
Where can I get blaze?
The source code and installation instructions are on GitHub: https://github.com/indexable-inc/blaze

Summary generated by AI from the project's README. GitHub stats refresh daily.

Related projects

asmjit / asmjit

A C++ library for low-latency machine code generation, letting programs emit x86/x64 and AArch64 instructions at runtime.

Developer Tools#jit#machine-code#assembler
4.6K+3 this week606C++ZlibWell maintainedUpdated 2 days ago