| Crates.io | hax-rust-engine-macros |
| lib.rs | hax-rust-engine-macros |
| version | 0.3.4 |
| created_at | 2025-09-03 11:31:26.3745+00 |
| updated_at | 2025-09-03 14:27:38.528526+00 |
| description | This crate provides helpers procedural macros for the `hax-rust-engine` |
| homepage | https://github.com/hacspec/hax |
| repository | https://github.com/hacspec/hax |
| max_upload_size | |
| id | 1822394 |
| size | 26,629 |
🌐 Website | 📝 Blog | 💬 Zulip | 🛝 Playground
hax is a tool for high assurance translations of a large subset of Rust into formal languages such as F* or Rocq.
hacspec is the functional subset of Rust that can be used, together with a hacspec standard library, to write succinct, executable, and verifiable specifications in Rust. These specifications can be translated into formal languages with hax.
Here are some resources for learning more about hax:
Hax is a cargo subcommand.
The command cargo hax accepts the following subcommands:
into (cargo hax into BACKEND): translate a Rust crate to the backend BACKEND (e.g. fstar, coq).json (cargo hax json): extract the typed AST of your crate as a JSON file.Note:
BACKEND can be fstar, coq, easycrypt or pro-verif. cargo hax into --help
gives the full list of supported backends.cargo hax, cargo hax into and cargo hax into <BACKEND> takes options. For instance, you can cargo hax into fstar --z3rlimit 100. Use --help on those subcommands to list
all options.git clone git@github.com:hacspec/hax.git && cd hax./setup.sh.cargo-hax --helpThis should work on Linux, MacOS and Windows.
curl --proto '=https' --tlsv1.2 -sSf -L https://install.determinate.systems/nix | sh -s -- install
Run hax on a crate directly to get F*/Coq/... (assuming you are in the crate's folder):
nix run github:hacspec/hax -- into fstar extracts F*.Install hax: nix profile install github:hacspec/hax, then run cargo hax --help anywhere
Note: in any of the Nix commands above, replace github:hacspec/hax by ./dir to compile a local checkout of hax that lives in ./some-dir
Setup binary cache: using Cachix, just cachix use hax
git clone git@github.com:hacspec/hax.git && cd haxdocker build -f .docker/Dockerfile . -t haxdocker run -it --rm -v /some/dir/with/a/crate:/work hax bashcargo-hax --help (notice here we use cargo-hax instead of cargo hax)Note: Please make sure that $HOME/.cargo/bin is in your $PATH, as
that is where setup.sh will install hax.
Hax intends to support full Rust, with the one exception, promoting a functional style: mutable references (aka &mut T) on return types or when aliasing (see https://github.com/hacspec/hax/issues/420) are forbidden.
Each unsupported Rust feature is documented as an issue labeled unsupported-rust. When the issue is labeled wontfix-v1, that means we don't plan on supporting that feature soon.
Quicklinks:
The documentation of the internal crate of hax and its engine can be found here for the engine and here for the frontend.
Just clone & cd into the repo, then run nix develop ..
You can also just use direnv, with editor integration.
rust-frontend/: Rust library that hooks in the rust compiler and
extract its internal typed abstract syntax tree
THIR as JSON.engine/: the simplification and elaboration engine that translates
programs from the Rust language to various backends (see engine/backends/).cli/: the hax subcommand for Cargo.We use the just command runner. If you use
Nix, the dev shell provides it automatically, if you don't use Nix,
please install just on
your system.
Anywhere within the repository, you can build and install in PATH (1)
the Rust parts with just rust, (2) the OCaml parts with just ocaml
or (3) both with just build. More commands (e.g. just fmt to
format) are available, please run just or just --list to get all
the commands.
Before starting any work please join the Zulip chat, start a discussion on Github, or file an issue to discuss your contribution.
Zulip graciously provides the hacspec & hax community with a "Zulip Cloud Standard" tier.