std::recursive_timed_mutex::try_lock_for (3) - Linux Man Pages
template< class Rep, class Period > (since C++11)
bool try_lock_for( const std::chrono::duration<Rep,Period>& timeout_duration );
Tries to lock the mutex. Blocks until specified timeout_duration has elapsed or the lock is acquired, 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 steady_clock is used to measure the duration. If an implementation uses a 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.
A thread may call try_lock_for on a recursive mutex repeatedly. Successful calls to try_lock_for increment the ownership count: the mutex will only be released after the thread makes a matching number of calls to unlock.
The maximum number of levels of ownership is unspecified. A call to try_lock_for will return false if this number is exceeded.
timeout_duration - minimum duration to block for
true if the lock was acquired successfully, otherwise false.
Any exception thrown by clock, time_point, or duration during the execution (clocks, time points, and durations provided by the standard library never throw)
// Run this code
lock (public member function)
try_lock (public member function)
try_lock_until unavailable until specified time point has been reached