11 21: New addition on 3.0.0 and 3.1.0 for 22: The go command profiles a real run, identifies the hottest portable functions to bridge individually into Rust crates, records use cases, writes tasks for agents like Claude and Codex, then builds, compares, and benchmarks. It only enables the changes if all checks pass. enable / disable inserts or removes markers in the original TypeScript, JavaScript, or Python files, allowing all callers to switch in-place to the Rust implementation or back to the original; report generates reports and cards suitable for PRs; package bundles the entire Node CLI tool into a multi-platform npm package. The ESLint port has already been published to npm as eslint-rs.
Why it matters Compared to yesterday's inclusion, the new go command first identifies the slowest functions and hands them off to agents for rewriting. It only reintegrates them into the original program if all comparisons pass and performance is not slower than before.
Stars 7440 (+777 / 24h)
Reasons
- 777 new stars in 24 hours, total stars 7440 (indicating attention only); MIT license
- The changelog notes that the wasm port called item-by-item from JS loops was 7.6 times slower than JIT, and previous
goversions would still enable it. Starting with 3.1.0, it benchmarks first; if slower, it stops and explains where the slowdown occurs.
Usage
- After running
cargo install rust-anything, executerust-anything go --agent claude -- python3 app.py. It profiles this run and hands the slowest parts to Claude Code. Without--agent, it only generates task descriptions; you can port them yourself and then run it again to continue.
Risks
go,record,diff, andbenchactually run the original program. For operations involving file writes, databases, or networks, run them in copies and test environments without production credentials.- eslint-rs only has binaries for macOS and Linux; on Windows, it still runs ESLint itself. The Prettier port is packaged but not yet released.