std::shared_lock release() method - how to use?

Question

Documentation on the method (https://en.cppreference.com/w/cpp/thread/shared_lock/release) sounds confusing to me:

disassociates the associated mutex without unlocking (i.e., releasing ownership of) it

I used to explore shared_lock and unique_lock based on the same mutex to implement read/write locking, but still can not grasp what's the point in disassociating the lock with the mutex it was built upon?

What could be a more or less real usecase?

John Zwinck · Accepted Answer · 2023-07-15T17:32:10.873

0

It seems analogous to std::unique_ptr::release() and you might use it in the same kind of places. For example if you have a lower-level API which requires a locked mutex to be passed in directly and it will unlock it later. Not a common use case, to be sure, but neither is std::unique_ptr::release().

edited Jul 15 '23 at 17:32

answered Jul 15 '23 at 17:16

John Zwinck

239,568
38
324
436

I think you mean std::unique_ptr::release. I think shared_ptr has no release – gerum Jul 15 '23 at 17:28
@gerum Yes thanks, edited. – John Zwinck Jul 15 '23 at 17:32

std::shared_lock release() method - how to use?

1 Answers1