github/reth
1
1
Fork 0
mirror of https://github.com/paradigmxyz/reth.git synced 2026-02-03 03:25:01 -05:00
Code Issues Packages Projects Releases Wiki Activity

chore: clippy happy (#8362)

Browse Source 
Co-authored-by: Alexey Shekhirin <a.shekhirin@gmail.com>
This commit is contained in:
Matthias Seitz
2024-05-23 13:24:20 +02:00
committed by GitHub
parent 155876d28c
commit 4250c33da1
28 changed files with 70 additions and 76 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
crates/storage/db/src/implementation/mdbx/cursor.rs
View File

@@ -191,8 +191,7 @@ impl<K: TransactionKind, T: DupSort> DbDupCursorRO<T> for Cursor<K, T> {
/// - Some(key), Some(subkey): a `key` item whose data is >= than `subkey`
/// - Some(key), None: first item of a specified `key`
/// - None, Some(subkey): like first case, but in the first key
/// - None, None: first item in the table
/// of a DUPSORT table.
/// - None, None: first item in the table of a DUPSORT table.
fn walk_dup(
&mut self,
key: Option<T::Key>,

18
crates/storage/provider/src/providers/database/provider.rs
View File

@@ -375,20 +375,20 @@ impl<TX: DbTxMut + DbTx> DatabaseProvider<TX> {
///
/// If UNWIND is false we will just read the state/blocks and return them.
///
/// 1. Iterate over the [BlockBodyIndices][tables::BlockBodyIndices] table to get all
/// the transaction ids.
/// 2. Iterate over the [StorageChangeSets][tables::StorageChangeSets] table
/// and the [AccountChangeSets][tables::AccountChangeSets] tables in reverse order to
/// reconstruct the changesets.
/// - In order to have both the old and new values in the changesets, we also access the
/// plain state tables.
/// 1. Iterate over the [BlockBodyIndices][tables::BlockBodyIndices] table to get all the
/// transaction ids.
/// 2. Iterate over the [StorageChangeSets][tables::StorageChangeSets] table and the
/// [AccountChangeSets][tables::AccountChangeSets] tables in reverse order to reconstruct
/// the changesets.
/// - In order to have both the old and new values in the changesets, we also access the
/// plain state tables.
/// 3. While iterating over the changeset tables, if we encounter a new account or storage slot,
/// we:
/// we:
/// 1. Take the old value from the changeset
/// 2. Take the new value from the plain state
/// 3. Save the old value to the local state
/// 4. While iterating over the changeset tables, if we encounter an account/storage slot we
/// have seen before we:
/// have seen before we:
/// 1. Take the old value from the changeset
/// 2. Take the new value from the local state
/// 3. Set the local state to the value in the changeset