8 commits

Author	SHA1	Message	Date
Matthijs Brobbel	c7851112a5	Rename salsa-2022 to salsa	2024-06-18 09:40:21 +02:00
Jack Rickard	5b8464c4f9	Support on-demand inputs ... This adds initial support for on-demand inputs by allowing new inputs to be created with only a shared reference to the database. This allows creating new inputs during a revision and therefore from inside tracked functions.	2022-09-15 21:25:53 +01:00
XFFXFF	6776919f39	give salsa_runtime a default implementation	2022-08-24 20:11:48 +08:00
XFFXFF	2912e60938	impl salsa_runtime_mut for all the tests	2022-08-24 19:00:21 +08:00
Charles Lew	7267452ff1	Implement Setter API	2022-08-22 19:22:47 +08:00
XFFXFF	74e220ec39	update some tests	2022-08-22 15:32:29 +08:00
Niko Matsakis	70b50a1813	fix formatting	2022-08-17 07:38:03 -04:00
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

Renamed from salsa-2022-tests/tests/accumulate-and-reuse.rs (Browse further)