Files
pallectrum/electrum
SomberNight 837fc1606c address_sync: change up_to_date to be private; no lock needed to read
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.
2022-04-08 20:33:13 +02:00
..
2021-04-30 19:43:53 +02:00
2021-03-21 00:36:23 -04:00
2021-03-21 00:36:23 -04:00
2022-03-02 11:42:49 +00:00
2021-04-08 19:49:43 +02:00
fix
2022-02-28 15:17:56 +01:00
2021-09-15 16:41:41 +02:00
2021-09-24 17:36:33 +02:00
2021-03-21 00:36:23 -04:00
2021-07-15 14:52:25 +00:00
2021-09-27 10:31:44 +02:00
2021-07-16 11:27:36 +02:00
2021-03-21 00:36:23 -04:00
2021-03-21 00:36:23 -04:00
2021-05-06 19:47:22 +09:00
2021-06-22 19:24:16 +02:00
2022-04-04 20:55:47 +02:00
2022-03-24 15:59:14 +01:00