Skip to content

use set for the StemPrunableNodeRegistry#90

Open
matkt wants to merge 30 commits intobesu-eth:mainfrom
matkt:feature/bin-trie-fix
Open

use set for the StemPrunableNodeRegistry#90
matkt wants to merge 30 commits intobesu-eth:mainfrom
matkt:feature/bin-trie-fix

Conversation

@matkt
Copy link
Copy Markdown
Contributor

@matkt matkt commented Feb 27, 2026

PR description

Use set for the StemPrunableNodeRegistry

Fixed Issue(s)

thomas-quadratic and others added 25 commits June 13, 2025 09:44
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Thomas Zamojski <thomas.zamojski@quadratic-labs.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
@github-actions
Copy link
Copy Markdown

  • I thought about the changelog.

Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Copy link
Copy Markdown
Contributor

@thomas-quadratic thomas-quadratic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fixes.
As far as I am concerned, this looks like a solid and working MVP, fullfilling the needs at the moment.
I would approve if I could :)

*/
public class StemPrunableNodeRegistry<K extends BitSequence<K>> {

private final List<K> prunableStems = new ArrayList<>();
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason why not use a Set here for efficiency ? And why wrap the set in its own class ? For clarity ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes good point I think we can use a set . It's more for clarity but if in the future we see that it's useless maybe we will unwrap it

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

used set

Signed-off-by: Karim Taam <karim.t2am@gmail.com>
…bin-trie-fix

Signed-off-by: Karim Taam <karim.t2am@gmail.com>

# Conflicts:
#	src/main/java/org/hyperledger/besu/ethereum/stateless/bintrie/pruning/StemPrunableNodeRegistry.java
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
@matkt matkt changed the title Feature/bin trie fix use set for the StemPrunableNodeRegistry Feb 27, 2026
Copy link
Copy Markdown

@garyschulte garyschulte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants