Merge bitcoin/bitcoin#26302: refactor: Use type-safe time point for CWallet::m_next_resend #1224
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backports bitcoin#26302
Original commit: 50cc8ef
Changes
NodeClock::now()instead ofGetTime()for type safetym_next_resendfromstd::atomic<int64_t>tostd::atomic<NodeClock::time_point>FastRandomContext{}.rand_uniform_delay()for type-safe random delay#include <util/time.h>to wallet.hDash-specific adaptations
std::atomicwrapper aroundm_next_resend(Dash uses atomic for thread safety).load()calls for atomic access in comparisonsOriginal PR description
GetTimeis not type-safe, thus deprecated.ACKs for top commit:
shaavan: Code Review ACK fa51cc9
aureleoules: ACK fa51cc9