uses struct instead of tuple for Merkle shreds variant #35303
Merged
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
Working towards adding a new Merkle shred variant with retransmitter's signature.
behzadnouri
force-pushed
the
merkle-variant-struct
branch
from
f91cacf to
79a6854
Compare
behzadnouri
requested review from
carllin,
steviez,
AshwinSekar and
bw-solana
|
Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis. |
mergify bot
pushed a commit
that referenced
this pull request
Feb 26, 2024
Working towards adding a new Merkle shred variant with retransmitter's signature, the commit uses struct instead of tuple to describe Merkle shred variant. (cherry picked from commit c8ee4f5)
mergify bot
added a commit
that referenced
this pull request
Feb 26, 2024
…rt of #35303) (#35321) uses struct instead of tuple for Merkle shreds variant (#35303) Working towards adding a new Merkle shred variant with retransmitter's signature, the commit uses struct instead of tuple to describe Merkle shred variant. (cherry picked from commit c8ee4f5) Co-authored-by: behzad nouri <[email protected]>
jeffwashington
pushed a commit
to jeffwashington/solana
that referenced
this pull request
Feb 27, 2024
…5303) Working towards adding a new Merkle shred variant with retransmitter's signature, the commit uses struct instead of tuple to describe Merkle shred variant.
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.
Problem
Working towards adding a new Merkle shred variant with retransmitter's signature.
Summary of Changes
The commit uses struct instead of tuple for Merkle shreds variant.
This is part of #35293 factored out into its own commit.