Boost C++ Libraries: Ticket #2637: Request for shared_mutex duration timed_lock and timed_lock_shared

type, component, severity changed; owner set

mur@… — Mon, 05 Jan 2009 13:28:08 GMT

owner set to Anthony Williams
type Bugs → Feature Requests
component None → thread
severity Problem → Optimization

owner, status changed

viboes — Sat, 07 Jan 2012 23:40:14 GMT

owner changed from Anthony Williams to viboes
status new → assigned

description, summary changed

viboes — Mon, 12 Mar 2012 22:42:42 GMT

description modified (diff)
summary shared mutex lock → Request for shared_mutex duration timed_lock and timed_lock_shared

viboes — Mon, 12 Mar 2012 22:52:03 GMT

These functions are already committed. Only the documentation is missing and I will deprecated them once I include the try_lock_for and try_lock_shared_for functions having as parameter a chrono::duration parameter.

    template <class Rep, class Period>
        bool try_lock_for(const std::chrono::duration<Rep, Period>& rel_time);
    template <class Clock, class Duration>
        bool
        try_lock_until(
                      const std::chrono::time_point<Clock, Duration>& abs_time);
    template <class Rep, class Period>
        bool
        try_lock_shared_for(const std::chrono::duration<Rep, Period>& rel_time);
    template <class Clock, class Duration>
        bool
        try_lock_shared_until(
                      const std::chrono::time_point<Clock, Duration>& abs_time);

Would this respond to your request once the chrono based interface is released?

milestone changed

viboes — Sat, 31 Mar 2012 15:25:43 GMT

milestone Boost 1.38.0 → Boost 1.50.0

mur@… — Mon, 02 Apr 2012 07:45:01 GMT

Would this respond to your request once the chrono based interface is released?

Yes.

Will there be the absolute time used internally? What happens if the system clock is altered in between?

status changed; resolution set

viboes — Mon, 28 May 2012 15:10:14 GMT

status assigned → closed
resolution → fixed

Committed in release branch at [78543]