Tries to lock the mutex. Blocks until the specified duration timeout_duration has elapsed (timeout) or the lock is acquired (owns the mutex), whichever comes first. On successful lock acquisition returns true, otherwise returns false.
If timeout_duration is less or equal timeout_duration.zero(), the function behaves like try_lock().
This function may block for longer than timeout_duration due to scheduling or resource contention delays.
The standard recommends that a std::steady_clock is used to measure the duration. If an implementation uses a std::system_clock instead, the wait time may also be sensitive to clock adjustments.
As with try_lock(), this function is allowed to fail spuriously and return false even if the mutex was not locked by any other thread at some point during timeout_duration.
Prior unlock() operation on the same mutex synchronizes-with (as defined in std::memory_order) this operation if it returns true.
If try_lock_for is called by a thread that already owns the mutex, the behavior is undefined.
true if the lock was acquired successfully, otherwise false.
[edit] ExceptionsAny exception thrown by timeout_duration (durations provided by the standard library never throw).
[edit] ExamplePossible output:
[0] failed failed failed [3] failed failed success [2] failed success failed [1] success failed successDefect reports
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
DR Applied to Behavior as published Correct behavior LWG 2093 C++11try_lock_for threw nothing throws timeout-related exceptions [edit] See also locks the mutex, blocks if the mutex is not available
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4