-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
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
Remove genesis_block lazy initialization #756
Conversation
Hey, thanks for your contribution :)
Regarding |
Thanks @danielabrozzoni! I've updated my commit and ensured compact_filters compiles successfully.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should also update the Cargo.toml
to remove lazy_static from the compact_filters feature since it's not needed anymore.
Actually I think you may even be able to remove the lazy_static dependency (not the dev-dependency which is used in the tests) entirely, I don't think it's used anywhere else
Got it, and thank you for taking a look! I've updated the commit after removing the dependency (but not dev-dependency). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested ACK. Thanks for the contribution!
Code looks good to me, can you please squash all commits? You have three separate commits with the same title/message, it should be just one. |
This commit contains a change to address issue bitcoindevkit#752 cargo test runs successfully.
Done! Thanks for the link. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK e6f2d02
Description
This commit fixes #752
cargo test runs successfully.
Notes to the reviewers
Hi, newbie here learning Rust and BDK! I've removed the lazy_static block in this commit, and when learning about lazy_static also came across something called once_cell, soon to be available in stdlib. It's like lazy_static but faster and is not a macro. Shall I keep the lazy_static and create an issue to switch to once_cell in the future, or remove the lazy_static (as I've done) and create an issue anyway?
All Submissions:
cargo fmt
andcargo clippy
before committing