boost - Is there an analog for std::lock/std::try_lock for try_lock_for and try_lock_until? -
When receiving multiple mutues (or with an boost, an Iterator range of mutecus), we lock the deadlock order There are similar There is also the concept, which combines methods like Similarly, there are Execution actions avoided planned for No, I have no proposal to add those functions. I believe there is no past proposal, but maybe I've missed for a year before the C ++ 0x process. I think the use of those functions will be very less common for the use of std :: try_lock and
boost :: try_lock functions using the lockable concept.
Try_lock_for and
try_lock_until add timeout words to
try_lock . What are the plans for analog, which provide convenience to avoid deadlock and timeout semantic (possibly
std :: try_lock_for (Lockable1 & lock1, Lockable2 and lock2, LockableN & amp; lockn ...) < / Code> and
std:: Try_lock_until (Lockable1 & Lock1, Lockable2 & lock2, LockableN & lockkn ...) )
lock_shared ,
try_lock_shared ,
try_lock_shared_for , and
try_lock_shared_until ?
std :: lock and
std: try_lock
Comments
Post a Comment