concurrency fixes for garbage collection #81
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@alex-ozdemir reminded me that tests run concurrently, meaning we actually have to worry about deadlocking etc in the garbage collector. Mea culpa.
This PR makes the collector hold one lock (on TERMS, TYPES, or FOLDS) at a time.
It also adds a new lock, COLLECT, only in
#[cfg(test)]
. The collector takes this read-write; constant-folding and type-checking take it read-only. This means that garbage collection can't run while folding or typing is going on, which otherwise could potentially result in terms being collected while they're still needed.