diff options
| author | fanquake <fanquake@gmail.com> | 2020-06-05 10:12:59 +0800 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2020-06-05 11:01:39 +0800 |
| commit | 4ede05d421e7799e631bb83ed16799e8bae79eeb (patch) | |
| tree | d5db7a1cdad94234b8a05231ffc0f248cbd6c5bc /src/test/arith_uint256_tests.cpp | |
| parent | 01b45b2e016f0b0907929e818216edf7157fb03a (diff) | |
| parent | 89f9fef1f71dfeff4baa59bc42bc9049a46d911b (diff) | |
Merge #18758: Remove unused boost/thread
89f9fef1f71dfeff4baa59bc42bc9049a46d911b refactor: Specify boost/thread/thread.hpp explicitly (Hennadii Stepanov)
fad8c890f5ae6e083e416781b4857a1a53ad5249 txdb: Remove unused boost/thread (MarcoFalke)
faa958bc283023334b9377f5fb2210459ca16d82 txindex: Remove unused boost/thread (MarcoFalke)
Pull request description:
There are predefined interruption points for `boost::thread`: https://www.boost.org/doc/libs/1_71_0/doc/html/thread/thread_management.html#interruption_points
However, non-boost threads such as `std::thread` or the `main()` thread can obviously not be interrupted. So remove all unused boost/thread from methods that are never executed in a `boost::thread`.
Most of them were accompanied by a `ShutdownRequested` anyway. So even if the current thread was a `boost::thread`, the interruption point would be redundant. (We only interrupt threads during shutdown)
ACKs for top commit:
fanquake:
ACK 89f9fef1f71dfeff4baa59bc42bc9049a46d911b
hebasto:
ACK 89f9fef1f71dfeff4baa59bc42bc9049a46d911b, tested on Linux Mint 19.3 (x86_64), verified shutdown in different scenarios.
Tree-SHA512: 17221dadedf2d107e5bda9e4f371cc4f8ffce6ad27cae41aa2b8f1150d8f1adf23d396585ca4a2dd25b1dc6f0d5c81fecd950d8557966ccb45a6d4a85a331d90
Diffstat (limited to 'src/test/arith_uint256_tests.cpp')
0 files changed, 0 insertions, 0 deletions