A generic framework for on-demand, incrementalized computation. Inspired by adapton, glimmer, and rustc's query system.
Find a file
Niko Matsakis d0a105a193 devcontainer definition
Created by VSCode's command.
2024-07-28 10:16:36 +00:00
.devcontainer devcontainer definition 2024-07-28 10:16:36 +00:00
.github devcontainer definition 2024-07-28 10:16:36 +00:00
book Merge branch 'master' into remove-old-salsa 2024-06-18 13:00:17 +02:00
components move local state into thread local 2024-07-23 21:45:31 -04:00
examples remove RuntimeId and use ThreadId 2024-07-23 11:53:37 -04:00
src Merge pull request #532 from salsa-rs/fix-guard-assertion 2024-07-28 09:56:42 +00:00
tests Bump revision in db.synthetic_write 2024-07-26 15:56:51 +02:00
.dir-locals.el
.gitignore
Cargo.toml chore: use tracing instead of log 2024-07-22 18:02:40 -04:00
FAQ.md
LICENSE-APACHE
LICENSE-MIT
README.md Fix Chinese book link 2022-09-24 01:00:36 +09:00
RELEASES.md

salsa

Test Book Released API docs Crates.io

A generic framework for on-demand, incrementalized computation.

Salsa Logo

Obligatory warning

Very much a WORK IN PROGRESS at this point. Ready for experimental use but expect frequent breaking changes.

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:

Getting in touch

The bulk of the discussion happens in the issues and pull requests, but we have a zulip chat as well.