Move this S3ClientLock into a temporary instance It is counter-intuitive, but lock ordering issues can happen even with a shared mutex locked in shared mode. The reason is that locking again in shared mode can block while there are threads waiting to take the lock in exclusive mode. Therefore, we should avoid obtaining the S3ClientLock when we already have it locked. This methods helps by moving
| 870 | // |
| 871 | // (see GH-36523) |
| 872 | S3ClientLock Move() { return std::move(*this); } |
| 873 | |
| 874 | protected: |
| 875 | friend class S3ClientHolder; |
nothing calls this directly
no outgoing calls
no test coverage detected