We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
for use cases like
#10037
it is beneficial to have the block numbers in canonical order
currently we're using a regular hashmap:
reth/crates/chain-state/src/in_memory.rs
Lines 30 to 31 in 29dc8fc
we can easily find the lowest and highest block with a btreemap
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
for use cases like
#10037
it is beneficial to have the block numbers in canonical order
currently we're using a regular hashmap:
reth/crates/chain-state/src/in_memory.rs
Lines 30 to 31 in 29dc8fc
we can easily find the lowest and highest block with a btreemap
TODO
The text was updated successfully, but these errors were encountered: