A generic framework for on-demand, incrementalized computation. Inspired by adapton, glimmer, and rustc's query system.
Find a file
Niko Matsakis 9df075b63c reset accumulators on new revisions, etc
Accumulators don't currently work across revisions
due to a few bugs. This commit adds 2 tests to show
the problems and reworks the implementation strategy.

We keep track of when the values in an accumulator were pushed
and reset the vector to empty when the push occurs in a new
revision.

We also ignore stale values from old revisions
(but update the revision when it is marked as validated).

Finally, we treat an accumulator as an untracked read,
which is quite conservative but correct. To get better
reuse, we would need to (a) somehow determine when different
values were pushed, e.g. by hashing or tracked the old values;
and (b) have some `DatabaseKeyIndex` we can use to identify
"the values pushed by this query".

Both of these would add overhead to accumulators and I didn'τ
feel like doing it, particularly since the main use case for
them is communicating errors and things which are not typically
used from within queries.
2022-08-17 06:47:11 -04:00
.github/workflows run cargo check --all in CI 2022-08-05 14:29:54 -04:00
book update reference chapter 2022-08-13 01:21:45 -04:00
calc-example/calc rename salsa-entity to salsa-2022 2022-08-05 13:20:14 -04:00
components reset accumulators on new revisions, etc 2022-08-17 06:47:11 -04:00
examples Remove ': salsa::Database' bound from two examples 2021-12-30 11:02:30 +00:00
salsa-2022-tests reset accumulators on new revisions, etc 2022-08-17 06:47:11 -04:00
src cargo fmt 2022-06-03 07:01:27 -04:00
tests broken tests 2022-06-03 06:08:57 -04:00
.dir-locals.el ask emacs to rustfmt on save 2018-09-28 11:26:57 -04:00
.gitignore update travis to test book and publish 2019-01-31 10:33:28 -05:00
bors.toml Update book workflow 2021-09-28 22:03:05 +02:00
Cargo.toml rename salsa-entity to salsa-2022 2022-08-05 13:20:14 -04:00
FAQ.md Update New Mexico state question 2020-06-26 15:48:29 +01:00
LICENSE-APACHE add readme, license, etc 2018-09-28 11:01:27 -04:00
LICENSE-MIT add readme, license, etc 2018-09-28 11:01:27 -04:00
README.md add the logo 2022-04-15 10:14:50 -04:00
RELEASES.md highlight breaking changes 2019-08-15 08:08:00 -04:00

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 is 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.