indexable-inc/ra-jit

选用指南

AI 根据 README 整理 · 2026/10/20 22:02:02

使用方式

通过 nix run 或 cargo build 运行，提供命令行界面。

查看 README 依据

# ra-jit Hot-reload Rust in milliseconds, using rust-analyzer as the compiler front end. ``` nix run github:indexable-inc/ra-jit ```  [mp4](docs/demo.mp4) Edit the source on the right and the Game of Life on the left changes on the next frame, with its state intact. A toggle switches to a real `cargo build` per edit for comparison. > [!WARNING]

`nix run` builds each crate as its own Nix derivation from cargo's unit graph, so editing ra-jit doesn't rebuild rust-analyzer or Cranelift. After changing `Cargo.toml` or `Cargo.lock`, regenerate the graph with `python3 tools/unit_graph.py`. Without nix: nightly-2026-07-15 with `rust-src`, then `cargo build --release && ./target/release/ra-jit life`. ## Thanks [rust-analyzer](https://github.com/rust-lang/rust-analyzer) does the hard part (parsing, types, traits, layouts, MIR). [Cranelift](https://cranelift.dev/) generates the code. [egui](https://github.com/emilk/egui) draws the window.

部署要求

需要 Nix 或 Rust nightly-2026-07-15 及 rust-src。

查看 README 依据

`nix run` builds each crate as its own Nix derivation from cargo's unit graph, so editing ra-jit doesn't rebuild rust-analyzer or Cranelift. After changing `Cargo.toml` or `Cargo.lock`, regenerate the graph with `python3 tools/unit_graph.py`. Without nix: nightly-2026-07-15 with `rust-src`, then `cargo build --release && ./target/release/ra-jit life`. ## Thanks [rust-analyzer](https://github.com/rust-lang/rust-analyzer) does the hard part (parsing, types, traits, layouts, MIR). [Cranelift](https://cranelift.dev/) generates the code. [egui](https://github.com/emilk/egui) draws the window.

已知限制

仅支持 rust-analyzer 能降低到 MIR 且 ra-jit 能翻译的 Rust 子集，不支持 dyn、闭包、堆、std/fmt、drop、unwinding 等，且无溢出和边界检查。

查看 README 依据

> **This is an experiment.** It only runs what rust-analyzer can lower to MIR and what ra-jit can translate. Today that is a small subset of Rust: no `dyn`, closures, heap, `std`/`fmt`, drops, unwinding or real `i128`, and no overflow or bounds checks. rust-analyzer has only partial borrow checking, so code rustc rejects may still run here. Keep running `cargo check`; rustc + LLVM stay the compiler for release builds and CI. > [!NOTE]