Skip to content

chore: release v0.3.1 #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: release v0.3.1 #23

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,17 @@

All notable changes to this project will be documented in this file.

## [0.3.1] - 2025-05-09

### BitVec

- Add missing operations from QF_BV (#21)

### Solver

- Add check_sat_assuming (#20)

<!-- generated by git-cliff -->
## [0.3.0] - 2025-03-19

This release changes how terms are stored. In 0.2.0 terms where all stored with `'static`, making them `Copy` and easy to move around. The downside being that any constructed term would stick around _forever_. To mitigate this memory leak, while retaining `Copy` semantics 0.3.0 introduces the concept of `Storage`. Essentially this means that terms are allocated in a shared buffer, arena style. This swaps out `&'static` with `&'st`, meaning that all terms now carry around a lifetime of their storage binding them to live exactly as long as that, and allowing the storage to be dropped and memory reclaimed as needed. The downside is that now one needs lifetime allocation and to pass a storage. The first downside is inevitable if we want statically enforced lifetimes, but we've tried to mitigate the second by storing pointers to storage in convenient places, allowing for writing stuff like `x + 2` and having the resulting term be allocated seamlessly. An upside of using arena allocation, is that we open the possibility to interning terms, strings and slices plus arranging things more compactly in memory.
Expand Down
6 changes: 3 additions & 3 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,14 +3,14 @@ members = ["smtlib", "lowlevel", "xtask"]
resolver = "2"

[workspace.package]
version = "0.3.0"
version = "0.3.1"
rust-version = "1.82"

[workspace.dependencies]
itertools = "0.14.0"
miette = { version = "7.0.0" }
serde = { version = "1.0.152", features = ["derive"] }
smtlib-lowlevel = { path = "./lowlevel", version = "0.3.0" }
smtlib-lowlevel = { path = "./lowlevel", version = "0.3.1" }
thiserror = "2.0"
insta = { version = "1.40.0", features = ["ron"] }
tokio = { version = "1.37.0", features = ["io-util", "process"] }
Expand Down