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
..
src	reset accumulators on new revisions, etc	2022-08-17 06:47:11 -04:00
Cargo.toml	rename salsa-entity to salsa-2022	2022-08-05 13:20:14 -04:00