diff options
| author | Wladimir J. van der Laan <laanwj@protonmail.com> | 2020-12-17 15:00:57 +0100 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@protonmail.com> | 2020-12-17 15:06:01 +0100 |
| commit | af4ce674dafade22cbeacc66d3aa5ca1b5c794f0 (patch) | |
| tree | 151aed671096cf6a8583579a0d3edf324c823ca9 /src/wallet/wallet.cpp | |
| parent | cfbfd389f6dd21cf4a78554ffe23fe2c54e0a8e4 (diff) | |
| parent | cc3044ccdbefa9fae58d1762477e377883b39c5e (diff) | |
| download | bitcoin-af4ce674dafade22cbeacc66d3aa5ca1b5c794f0.tar.xz | |
Merge #20635: fix misleading comment about call to non-existing function
cc3044ccdbefa9fae58d1762477e377883b39c5e fix misleading comment about call to non-existing function (pox)
Pull request description:
The comment seems to be describing the subsequent call to `SyncTransaction` but refers to it as `SyncNotifications`, which is not any function currently in the codebase.
It's best to just remove the "what" aspect of the comment and focus on the "why", which also reduces the risk of similar documentation errors in the future, in case the function ever gets renamed, for example.
ACKs for top commit:
laanwj:
ACK cc3044ccdbefa9fae58d1762477e377883b39c5e
Tree-SHA512: 882ff17836ef585a603dc504f3dd21f56f682e49b28a0998f23fd16025826fbb083b7978db3ee70d0e0ff2c86fd6c3fd99a2361e5d45c765fdc5822c5f14c0a7
Diffstat (limited to 'src/wallet/wallet.cpp')
| -rw-r--r-- | src/wallet/wallet.cpp | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/src/wallet/wallet.cpp b/src/wallet/wallet.cpp index 3e37491a23..740e671595 100644 --- a/src/wallet/wallet.cpp +++ b/src/wallet/wallet.cpp @@ -1178,9 +1178,8 @@ void CWallet::transactionRemovedFromMempool(const CTransactionRef& tx, MemPoolRe // Handle transactions that were removed from the mempool because they // conflict with transactions in a newly connected block. if (reason == MemPoolRemovalReason::CONFLICT) { - // Call SyncNotifications, so external -walletnotify notifications will - // be triggered for these transactions. Set Status::UNCONFIRMED instead - // of Status::CONFLICTED for a few reasons: + // Trigger external -walletnotify notifications for these transactions. + // Set Status::UNCONFIRMED instead of Status::CONFLICTED for a few reasons: // // 1. The transactionRemovedFromMempool callback does not currently // provide the conflicting block's hash and height, and for backwards |