test for excluded bounds in outputs_in_range#1897
test for excluded bounds in outputs_in_range#1897ValuedMammal merged 1 commit intobitcoindevkit:masterfrom
Conversation
|
tACK #1897 Tested and working as it should. |
ValuedMammal
left a comment
There was a problem hiding this comment.
ACK
@aagbotemi If you plan to rebase I left a comment that I think would make the test better.
9f16a42 to
8a86594
Compare
@ValuedMammal I have rebased and attended to the comment. Thank you. |
|
ACK 8a86594 pending a passing CI run. |
83cc556 to
d8819c3
Compare
@ValuedMammal I have rebased with PR #1972, that will fix the CI as discussed |
| let outputs_to_three_excl: Vec<_> = spk_index | ||
| .outputs_in_range((Bound::Included(4u32), Bound::Unbounded::<u32>)) | ||
| .collect(); |
There was a problem hiding this comment.
You might have meant to do Bound::Excluded(3) here.
There was a problem hiding this comment.
Yes, thank you for pointing it out. Using Bound::Excluded(3) provides clarity.
d8819c3 to
c39ba0a
Compare
notmandatory
left a comment
There was a problem hiding this comment.
ACK c39ba0a
Just needs a rebase to pick up a CI change and then it looks ready to merge.
- replace range syntax with explicit Bound types in outputs_in_range tests
c39ba0a to
ad79267
Compare
Thank you for the feedback. I have rebased |
|
ACK ad79267 |
Description
This PR covers a wide range on tests for excluded bounds and the
SpkTxOutIndex::outputs_in_range. This PR fixes bitcoindevkit/bdk_wallet#58Notes to the reviewers
Changelog notice
Checklists
All Submissions:
cargo fmtandcargo clippybefore committingNew Features:
Bugfixes: