Re: [boost] Boost.Fiber mini-review September 4-13

Subject: Re: [boost] Boost.Fiber mini-review September 4-13
From: Oliver Kowalke (oliver.kowalke_at_[hidden])
Date: 2015-09-04 22:12:36

2015-09-04 22:18 GMT+02:00 Agustín K-ballo Bergé <kaballo86_at_[hidden]>:

> On 9/4/2015 5:04 PM, Oliver Kowalke wrote:
>
>> 2015-09-04 21:35 GMT+02:00 Agustín K-ballo Bergé <kaballo86_at_[hidden]>:
>>
>> Here is the standard definition of `future::wait_until`:
>>>
>>>      template <class Clock, class Duration>
>>>      future_status wait_until(chrono::time_point<Clock, Duration> const&
>>> abs_time) const;
>>>
>>> Note how it takes *any* time point, and automatically deduces template
>>> arguments.
>>>
>>>
>> I use this pattern in the other classes too (for instance
>> condition::wait_until())
>>
>>
> Is there anything particular about `future` and `shared_future` that
> prevents you from doing it correctly for them too?
>

no, it is fixed in branch develop - I missed to fix it as I changed the
chrono related code in the other classes