Move replaying to own module & remove replay fieds from CommittedState
#4055
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of Changes
This moves replaying logic out of
LockingandCommittedStateand into its own module.The special fields that were only used in
CommittedStateare also removed, so that we don't pay that cost forever after replay has finished. This removes 96 bytes from the size ofCommittedState.API and ABI breaking changes
None
Expected complexity level and risk
2? Replay is fairly sensitive code. However, this is mostly code motion. Care has been taken to prevent deadlocks.
Testing
Covered by existing tests since this is code motion.