由Indexable Inc.推出的Rust增量构建工具Blaze于2026年10月24日正式更名并发布 1。在真实项目的平均测试中,该工具展现出显著的构建速度优势 1。具体数据显示,在macOS arm64平台上,其编辑重建速度比cargo build快10倍;在Linux aarch64上快24倍;而在Linux x86-64上则快11倍 1。
Blaze的核心机制在于保持项目在内存中进行编译,仅重新编译发生更改的函数并将结果写入已构建的程序中,从而避免了从头开始的链接过程 1。这种设计使得从保存文件到使用新代码运行程序的延迟大约仅为20毫秒,实现了针对实时编辑场景的毫秒级重建 1。
目前,Blaze主要支持macOS(Apple silicon)和Linux平台,而在Windows环境下仍继续使用cargo进行构建 1。首次构建时工具会运行cargo,随后由blaze引擎接管后续工作 1。虽然该项目采用了独立的Rust工具链版本(标识为blaze-2026-10-25),但它尊重项目的toolchain配置作为最终权威 1。值得注意的是,这种极致的速度提升是以消耗几GB内存为代价的 1。鉴于项目仍处于早期阶段,官方建议开发者保留cargo作为最终的校验工具 1。Blaze依赖于rust-analyzer、Cranelift、LLVM和salsa等技术,并以MIT或Apache-2.0许可证开源 1。
Indexable Inc. has released Blaze, a new incremental build tool for Rust that claims compilation speeds up to 92 times faster than the standard cargo/rustc toolchain 1. The project was renamed from its previous identity, ra-jit, on October 24, 2026, and is currently in its early stages 1. It is available under an MIT or Apache-2.0 license 1.
Blaze operates by keeping the project compiled in memory and only recompiling modified functions, avoiding the need to relink the entire program from scratch 1. While the initial build utilizes cargo, subsequent changes are handled by the Blaze engine, which writes updated code directly into the built program 1. This approach aims to reduce the time from saving a file to running the program with new code to approximately 20 milliseconds in live editing scenarios 1.
Performance benchmarks cited by the developers indicate average speedups of 10 times on macOS arm64, 24 times on Linux aarch64, and 11 times on Linux x86-64 when comparing edit-rebuild cycles against cargo build 1. These performance gains come at the cost of higher memory usage, requiring several gigabytes of RAM to maintain the in-memory state 1. The tool relies on dependencies such as rust-analyzer, Cranelift, LLVM, and salsa 1.
Blaze supports macOS (Apple Silicon) and Linux platforms; however, builds on Windows environments continue to use cargo 1. Although Blaze uses its own distinct Rust toolchain version labeled blaze-2026-10-25, it respects the project's configured toolchain as the final authority 1. Due to the project's current maturity level, developers recommend retaining cargo as a verification tool 1.
评论
还没有评论,欢迎留下第一条。