diff options
author | MarcoFalke <falke.marco@gmail.com> | 2020-06-08 06:54:53 -0400 |
---|---|---|
committer | MarcoFalke <falke.marco@gmail.com> | 2020-06-08 06:55:00 -0400 |
commit | 399a0d9dc7a15bd4a9184ba19e1f251cfbb450c8 (patch) | |
tree | c4e0cb9b77b89f1c0d0cd3d16a22b2e5931e4d9c /.tx/config | |
parent | 807b9f811479a2b5a4b29e44fe915e054bd92fc3 (diff) | |
parent | 1a9ef1d398dd14728b6bc67a89139cdf827c9753 (diff) |
Merge #19180: refactor: Replace RecursiveMutex with Mutex in Shutdown()
1a9ef1d398dd14728b6bc67a89139cdf827c9753 refactor: Replace RecursiveMutex with Mutex in Shutdown() (Hennadii Stepanov)
Pull request description:
Step by step, going to replace all of the `RecursiveMutex` instances with the `Mutex` ones throughout the code base :)
Not sure if it is possible in all cases though...
This one is a low-hanging fruit.
ACKs for top commit:
MarcoFalke:
ACK 1a9ef1d398dd14728b6bc67a89139cdf827c9753 Shutdown is not recursive, so the same thread can never lock twice (UB)
vasild:
ACK 1a9ef1d3 verified manually that `Shutdown()` is not called from places that could be called from inside `Shutdown()`.
Tree-SHA512: 362a507b1a6f97dc351f708224aedbfe4bee03c4398f394d78ee31c24d76a7012ffff0e6766866cd5fd9a8e0d8840f05a2741111fe583aa20d45f0af3df0dcfa
Diffstat (limited to '.tx/config')
0 files changed, 0 insertions, 0 deletions