mock-consensus: 👷 block data is implicitly empty, can be appended #4004
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
cratelyn
force-pushed
the
kate/mock-consensus-block-builder-data-is-implicitly-empty
branch
from
13f71f0 to
7bc540a
Compare
|
force pushed and rebased off of |
cratelyn
deleted the
kate/mock-consensus-block-builder-data-is-implicitly-empty
branch
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.
fixes #3936. based upon #4002. see #3588.
this changes the type of the block builder's
data, allowing it to be implicitly kept empty. this is useful when e.g. fast forwarding a number of blocks (see #4002). this spares us the need to callwith_data(vec![]), and additionally means that the block builder is never in an uninitialized state (making #4003 needless).add_txto append tx's #3936fast_forward#4002Apptests #3588