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

ra_ap_salsa

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

16 releases

new 0.0.216 May 20, 2024
0.0.215 May 13, 2024
0.0.213 Apr 29, 2024
0.0.207 Mar 25, 2024
0.0.203 Feb 26, 2024

#349 in Development tools

Download history 100/week @ 2024-02-10 188/week @ 2024-02-17 746/week @ 2024-02-24 679/week @ 2024-03-02 491/week @ 2024-03-09 689/week @ 2024-03-16 676/week @ 2024-03-23 614/week @ 2024-03-30 780/week @ 2024-04-06 744/week @ 2024-04-13 569/week @ 2024-04-20 495/week @ 2024-04-27 564/week @ 2024-05-04 472/week @ 2024-05-11

2,160 downloads per month
Used in 21 crates (2 directly)

Apache-2.0 OR MIT

175KB
3K 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–9MB
~66K SLoC