This repository has been archived by the owner on Nov 24, 2022. It is now read-only.
Clean dirty closures during scavenging #476
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
acondolu
force-pushed
the
wip-dirty-clean
branch
from
ac86348
to
6604518
Compare
acondolu
force-pushed
the
wip-dirty-clean
branch
2 times, most recently
from
9c10e0d
to
e3a7897
Compare
TerrorJack
force-pushed
the
wip-dirty-clean
branch
2 times, most recently
from
0807d87
to
32b271b
Compare
TerrorJack
force-pushed
the
wip-dirty-clean
branch
from
32b271b
to
4b501f4
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR changes the scavenging behaviour as follows: the headers marked as dirty are simply set as clean during GC.