refactor: remove Default
contraint in merkle tree trait
#1004
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.
Remove
Default
contraint inIsMerkleTreeBackend
Description
Previously, the
IsMerkleTreeBackend
trait required types to implement theDefault
trait. However,Default
is no longer used in the current Merkle tree construction logic.Requiring
Default
can be unnecessarily restrictive, especially in codebases where implementing it is non-trivial. This change simplifies the trait by removing the Default constraint, making it easier to implement custom backends.Type of change
Checklist