https://github.com/prove-rs/z3.rs

Rust bindings for the Z3 solver.
https://github.com/prove-rs/z3.rs

ffi-bindings logic-programming rust rust-bindings smt smt-solver

Last synced: 3 days ago
JSON representation

Rust bindings for the Z3 solver.

• Host: GitHub
• URL: https://github.com/prove-rs/z3.rs
• Owner: prove-rs
• Created: 2018-03-08T16:19:05.000Z (almost 8 years ago)
• Default Branch: master
• Last Pushed: 2024-12-09T11:44:54.000Z (about 1 year ago)
• Last Synced: 2025-05-07T08:56:41.541Z (10 months ago)
• Topics: ffi-bindings, logic-programming, rust, rust-bindings, smt, smt-solver
• Language: Rust
• Homepage:
• Size: 645 KB
• Stars: 391
• Watchers: 9
• Forks: 122
• Open Issues: 72
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• awesome-rust-formalized-reasoning - z3 - sys):star::fire: - high-level and low-level Rust bindings for the Z3 solver. (Projects / Libraries)

README

          
# `z3` and `z3-sys`

[![Rust](https://github.com/prove-rs/z3.rs/actions/workflows/rust.yml/badge.svg)](https://github.com/prove-rs/z3.rs/actions/workflows/rust.yml)

This repository contains [high-level][z3] and [low-level][z3-sys] Rust bindings

for the [Z3 solver][upstream].

[upstream]: https://github.com/Z3Prover/z3

[z3]: https://github.com/prove-rs/z3.rs/tree/master/z3

[z3-sys]: https://github.com/prove-rs/z3.rs/tree/master/z3-sys

## `z3`

[![](https://img.shields.io/crates/v/z3.svg)](https://crates.io/crates/z3)

The [`z3` crate][z3] provides high-level bindings to the Z3 solver. It is built

on top of, and wraps, the `z3-sys` crate. This is the crate you'll want to use

99% of the time.

## `z3-sys`

[![](https://img.shields.io/crates/v/z3-sys.svg)](https://crates.io/crates/z3-sys)

The [`z3-sys` crate][z3-sys] provides the raw, unsafe, low-level C API that Z3

exposes.

## When should I use `z3-sys` instead of `z3`?

The first scenario where it makes sense to use `z3-sys` directly is when some Z3

feature isn't wrapped into high-level bindings in the `z3` crate yet. In this

case, it is worth filing an issue and discussing its implementation in the `z3`

crate, but you can get at the raw, underlying features via the `z3-sys` crate in

the meantime.

The only other time to use `z3-sys` directly would be if you are writing your

own custom high-level API for Z3, instead of using the `z3` crate.