#computation #query #framework #key #salsa #generic #on-demand

ra_ap_salsa

A generic framework for on-demand, incrementalized computation (experimental)

26 releases

new 0.0.226 Jul 22, 2024
0.0.225 Jul 15, 2024
0.0.222 Jun 24, 2024
0.0.217 May 27, 2024
0.0.203 Feb 26, 2024

#347 in Development tools

Download history 660/week @ 2024-03-31 821/week @ 2024-04-07 692/week @ 2024-04-14 527/week @ 2024-04-21 512/week @ 2024-04-28 545/week @ 2024-05-05 505/week @ 2024-05-12 875/week @ 2024-05-19 693/week @ 2024-05-26 777/week @ 2024-06-02 899/week @ 2024-06-09 577/week @ 2024-06-16 503/week @ 2024-06-23 541/week @ 2024-06-30 710/week @ 2024-07-07 721/week @ 2024-07-14

2,537 downloads per month
Used in 22 crates (2 directly)

Apache-2.0 OR MIT

205KB
4K SLoC

salsa

A generic framework for on-demand, incrementalized computation.

Obligatory warning

This is a fork of https://github.com/salsa-rs/salsa/ adjusted to rust-analyzer's needs.

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.

Dependencies

~2.4–8.5MB
~66K SLoC