Browse Source
After some consideration I am fairly certain there is no need to take wallet.lock in `is_up_to_date()`. Any caller that might want some kind of guarantees re the value returned by is_up_to_date() would need to enforce them itself by e.g. taking wallet.lock around its critical code block. That is, even if is_up_to_date() itself takes the lock, between the call returning and the caller reading the value there could still have been a race. Also, the GUI was directly accessing the field already.patch-4
SomberNight
3 years ago
5 changed files with 13 additions and 13 deletions
Loading…
Reference in new issue