mirrors/salsa
1
0
Fork 0
mirror of https://github.com/salsa-rs/salsa.git synced 2025-01-23 13:10:19 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

remove outdated note on atomicity; not a concern anymore

Browse source
This commit is contained in:
Niko Matsakis 2018-11-01 05:03:09 -04:00
parent 341619d20e
commit d689d02117
1 changed files with 0 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
src/lib.rs
View file

@ -44,17 +44,6 @@ pub trait Database: plumbing::DatabaseStorageTypes + plumbing::DatabaseOps {
/// consume are marked as used. You then invoke this method to /// consume are marked as used. You then invoke this method to
/// remove other values that were not needed for your main query /// remove other values that were not needed for your main query
/// results. /// results.
///
/// **A note on atomicity.** Since `sweep_all` removes data that
/// hasn't been actively used since the last revision, executing
/// `sweep_all` concurrently with `set` operations is not
/// recommended. It won't do any *harm* -- but it may cause more
/// data to be discarded then you expect, leading to more
/// re-computation. You can use the [`lock_revision`][] method to
/// guarantee atomicity (or execute `sweep_all` from the same
/// threads that would be performing a `set`).
///
/// [`lock_revision`]: struct.Runtime.html#method.lock_revision
fn sweep_all(&self, strategy: SweepStrategy) { fn sweep_all(&self, strategy: SweepStrategy) {
self.salsa_runtime().sweep_all(self, strategy); self.salsa_runtime().sweep_all(self, strategy);
} }