ledger: turn deferredCommitContext.newBase into a function #5093
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.
Summary
Based on observations from #4419 it seems like deferredCommitContext.newBase is always set to the value of oldBase + offset, and is only stored on the DCC struct for code deduplication / convenience reasons. To enforce the invariant that newBase is always oldBase+offset and guard against bugs if this were not true, this turns it into a function rather than an assigned struct field.
Test Plan
Existing tests updated and should pass.