π¬ furszy commented on pull request "wallet: group outputs only once, decouple it from Coin Selection":
(https://github.com/bitcoin/bitcoin/pull/25806#issuecomment-1454159231)
Rebased it due silent merge conflicts with #26889.
Ready to go now.
(https://github.com/bitcoin/bitcoin/pull/25806#issuecomment-1454159231)
Rebased it due silent merge conflicts with #26889.
Ready to go now.
π hernanmarino opened a pull request: "Fixed typos in comments to make linter happy"
(https://github.com/bitcoin/bitcoin/pull/27197)
While working on a different PR, I stumbled upon and fixed a couple of typos being reported by the linter.
(https://github.com/bitcoin/bitcoin/pull/27197)
While working on a different PR, I stumbled upon and fixed a couple of typos being reported by the linter.
π hernanmarino's pull request is ready for review: "Fixed typos in comments to make linter happy"
(https://github.com/bitcoin/bitcoin/pull/27197)
(https://github.com/bitcoin/bitcoin/pull/27197)
π¬ theuni commented on pull request "util: add missing include and fix function signature":
(https://github.com/bitcoin/bitcoin/pull/27192#discussion_r1125077264)
Reordered. I think this change is simple enough for manual review :)
(https://github.com/bitcoin/bitcoin/pull/27192#discussion_r1125077264)
Reordered. I think this change is simple enough for manual review :)
π¬ Xekyo commented on pull request "Implement Mini version of BlockAssembler to calculate mining scores":
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1123812481)
Iβd probably prefer using `.value()` for new code Iβd write, but the asterisk-variant seems prevalent throughout this code.
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1123812481)
Iβd probably prefer using `.value()` for new code Iβd write, but the asterisk-variant seems prevalent throughout this code.
π¬ Xekyo commented on pull request "Implement Mini version of BlockAssembler to calculate mining scores":
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1123811383)
Yes, agreed using an optional would be more explicit, however handling the optional return value would touch a bunch of lines here, and given that the result should never be empty unless something went wrong or the function got called with an empty `txids` input, I feel itβs a bit of a cosmetic improvement here.
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1123811383)
Yes, agreed using an optional would be more explicit, however handling the optional return value would touch a bunch of lines here, and given that the result should never be empty unless something went wrong or the function got called with an empty `txids` input, I feel itβs a bit of a cosmetic improvement here.
π¬ Xekyo commented on pull request "Implement Mini version of BlockAssembler to calculate mining scores":
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1123823270)
Thanks, will consider, change but feel itβs okay at this time.
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1123823270)
Thanks, will consider, change but feel itβs okay at this time.
π¬ Xekyo commented on pull request "Implement Mini version of BlockAssembler to calculate mining scores":
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1123754749)
Iβve removed the `reserve(β¦)` call here.
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1123754749)
Iβve removed the `reserve(β¦)` call here.
π¬ Xekyo commented on pull request "Implement Mini version of BlockAssembler to calculate mining scores":
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1123819758)
As above with `GetIterVec()`, an empty vector is not a valid outcome for a call, so I tend to leave as is.
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1123819758)
As above with `GetIterVec()`, an empty vector is not a valid outcome for a call, so I tend to leave as is.
π¬ Xekyo commented on pull request "Implement Mini version of BlockAssembler to calculate mining scores":
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1124908789)
Updated
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1124908789)
Updated
π¬ Xekyo commented on pull request "Implement Mini version of BlockAssembler to calculate mining scores":
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1125071450)
Thanks, Iβm not going to interfere here, because outpoints are tiny anyway, and it seems more readable without the move or constructor.
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1125071450)
Thanks, Iβm not going to interfere here, because outpoints are tiny anyway, and it seems more readable without the move or constructor.
π¬ Xekyo commented on pull request "Implement Mini version of BlockAssembler to calculate mining scores":
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1124956187)
Thanks thatβs much nicer
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1124956187)
Thanks thatβs much nicer
π¬ Xekyo commented on pull request "Implement Mini version of BlockAssembler to calculate mining scores":
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1125071911)
Iβll have to revisit this one.
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1125071911)
Iβll have to revisit this one.
π¬ Xekyo commented on pull request "Implement Mini version of BlockAssembler to calculate mining scores":
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1124966759)
It seems to me that if we donβt use the result of `find`, itβs clearer that we just care about whether a key is present instead of where in the sequence it appears
(https://github.com/bitcoin/bitcoin/pull/27021#discussion_r1124966759)
It seems to me that if we donβt use the result of `find`, itβs clearer that we just care about whether a key is present instead of where in the sequence it appears
π¬ Xekyo commented on pull request "Bump unconfirmed ancestor transactions to target feerate":
(https://github.com/bitcoin/bitcoin/pull/26152#issuecomment-1454249283)
Rebased on latest version of #27021
(https://github.com/bitcoin/bitcoin/pull/26152#issuecomment-1454249283)
Rebased on latest version of #27021
π yahiheb approved a pull request: "Fix typos in comments to make linter happy"
(https://github.com/bitcoin/bitcoin/pull/27197)
(https://github.com/bitcoin/bitcoin/pull/27197)
π kristapsk approved a pull request: "Fix typos in comments to make linter happy"
(https://github.com/bitcoin/bitcoin/pull/27197)
utACK 987f1bb41c0a8c54422066e10d1c63e19c4df66d
(https://github.com/bitcoin/bitcoin/pull/27197)
utACK 987f1bb41c0a8c54422066e10d1c63e19c4df66d
π fanquake merged a pull request: "Fix typos in comments to make linter happy"
(https://github.com/bitcoin/bitcoin/pull/27197)
(https://github.com/bitcoin/bitcoin/pull/27197)
π fanquake approved a pull request: "util: add missing include and fix function signature"
(https://github.com/bitcoin/bitcoin/pull/27192)
ACK 8847ce44e0713350a6d3524f62eaeb10ba548bae
(https://github.com/bitcoin/bitcoin/pull/27192)
ACK 8847ce44e0713350a6d3524f62eaeb10ba548bae
π fanquake merged a pull request: "util: add missing include and fix function signature"
(https://github.com/bitcoin/bitcoin/pull/27192)
(https://github.com/bitcoin/bitcoin/pull/27192)