Rust Runtime

This guide walks through using Rust with poly-bench, from init through run. It covers what gets created, how dependencies work, and common gotchas.

Prerequisites

You need Rust installed and available on your PATH. The table below summarizes the requirements.

Install from rustup.rs. If Rust is missing when you run init, poly-bench can offer to install it interactively during poly-bench init.

Init

When you run poly-bench init --languages rust (or select Rust in the interactive flow), poly-bench creates a Cargo project under .polybench/runtime-env/rust/:

1.polybench/runtime-env/rust/
2├── Cargo.toml
3└── src/
4  └── main.rs

The Cargo project uses edition 2021 and the binary name polybench_runner. Do not change the package or binary name; the poly-bench executor expects it.

Add Dependencies

To add Rust crates, use the add command with the --rs flag:

$poly-bench add --rs serde@1.0

The spec format is crate@version — for example, serde@1.0. Dependencies are stored in the manifest and added to Cargo.toml via cargo add.

Some crates require specific features to expose the APIs you need. Use the optional --features flag with comma-separated feature names — for example, --features keccak,sha3. This produces entries like tiny-keccak = { version = "2.0", features = ["keccak"] } in Cargo.toml.

For memory benchmarks, poly-bench automatically adds alloc_tracker = "0.5" when needed. Do not remove it if you are running alloc benchmarks.

Install

Running poly-bench install (or poly-bench build) runs cargo build to fetch and compile dependencies. Cargo resolves crates from crates.io and builds the project.

Build / Codegen

When you run poly-bench run, poly-bench generates Rust code, writes it to the project, and compiles with cargo build --release. The generated binary is named polybench_runner.

Gotchas and Troubleshooting