feat: trait-based storage API #12616
Open
+481
−163
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.
ref #12157
This PR introduces a way to customize how
DatabaseProvider
writes primitive types to storage. This is done by introducing the following traits:reth/crates/storage/storage-api/src/chain.rs
Lines 12 to 34 in 0f40ad2
Those are generic over provider and primitive types and allow to define type that given a specifc provider implementation knows how to use it to write given object to database.
Additionaly we define the actual
ChainStorage
trait which is responsible for givingDatabaseProvider
the storage implementations:reth/crates/storage/provider/src/providers/database/chain.rs
Lines 7 to 14 in 0f40ad2
This trait is required due to
DatabaseProvider
being generic overTX
andTypes
and thus not allowing us to express requirements through just a single bound likeStorage: ChainStorage<DatabaseProvider<???, N>, N::Primitives>