![]()
Some checks failed
Book / Book (push) Has been cancelled
Release-plz / Release-plz release (push) Has been cancelled
Release-plz / Release-plz PR (push) Has been cancelled
Test / Test (push) Has been cancelled
Test / Shuttle (push) Has been cancelled
Test / Miri (push) Has been cancelled
Test / Benchmarks (push) Has been cancelled
Book / Deploy (push) Has been cancelled
* add memory usage information hooks * gate memory usage API under `salsa_unstable` feature * use snapshot tests for memory usage API |
||
---|---|---|
.devcontainer | ||
.github | ||
benches | ||
book | ||
components | ||
examples | ||
src | ||
tests | ||
.dir-locals.el | ||
.gitignore | ||
Cargo.toml | ||
CHANGELOG.md | ||
FAQ.md | ||
justfile | ||
LICENSE-APACHE | ||
LICENSE-MIT | ||
README.md | ||
release-plz.toml | ||
RELEASES.md |
salsa
A generic framework for on-demand, incrementalized computation.
Obligatory warning
Very much a WORK IN PROGRESS at this point.
Credits
This system is heavily inspired by adapton, glimmer, and rustc's query system. So credit goes to Eduard-Mihai Burtescu, Matthew Hammer, Yehuda Katz, and Michael Woerister.
Key idea
The key idea of salsa
is that you define your program as a set of
queries. Every query is used like function K -> V
that maps from
some key of type K
to a value of type V
. Queries come in two basic
varieties:
- Inputs: the base inputs to your system. You can change these whenever you like.
- Functions: pure functions (no side effects) that transform your inputs into other values. The results of queries are memoized to avoid recomputing them a lot. When you make changes to the inputs, we'll figure out (fairly intelligently) when we can re-use these memoized values and when we have to recompute them.
Want to learn more?
To learn more about Salsa, try one of the following:
- read the heavily commented examples;
- check out the Salsa book;
- watch one of our videos.
Getting in touch
The bulk of the discussion happens in the issues and pull requests, but we have a zulip chat as well.
Contributing
To create a release and publish to crates.io, update the version
field in Cargo.toml.
After pushed, GitHub Actions will publish the crates to crates.io automatically.