Re: [PATCH 1/2] condition_variable: Report early wakeup of wait_until as no_timeout

2018-08-01 Thread Jonathan Wakely
On 20/07/18 17:49 +0100, Mike Crowe wrote: As currently implemented, condition_variable always ultimately waits against std::chrono::system_clock. This clock can be changed in arbitrary ways by the user which may result in us waking up too early or too late when measured against the

[PATCH 1/2] condition_variable: Report early wakeup of wait_until as no_timeout

2018-07-20 Thread Mike Crowe
As currently implemented, condition_variable always ultimately waits against std::chrono::system_clock. This clock can be changed in arbitrary ways by the user which may result in us waking up too early or too late when measured against the caller-supplied clock. We can't (yet) do much about

Re: [PATCH 1/2] condition_variable: Report early wakeup of wait_until as no_timeout

2018-07-20 Thread Jonathan Wakely
On 20/07/18 12:30 +0100, Mike Crowe wrote: On Friday 20 July 2018 at 11:53:38 +0100, Jonathan Wakely wrote: On 10/07/18 11:09 +0100, Mike Crowe wrote: > As currently implemented, condition_variable always ultimately waits > against std::chrono::system_clock. This clock can be changed in

Re: [PATCH 1/2] condition_variable: Report early wakeup of wait_until as no_timeout

2018-07-20 Thread Mike Crowe
On Friday 20 July 2018 at 11:53:38 +0100, Jonathan Wakely wrote: > On 10/07/18 11:09 +0100, Mike Crowe wrote: > > As currently implemented, condition_variable always ultimately waits > > against std::chrono::system_clock. This clock can be changed in arbitrary > > ways by the user which may result

Re: [PATCH 1/2] condition_variable: Report early wakeup of wait_until as no_timeout

2018-07-20 Thread Jonathan Wakely
On 10/07/18 11:09 +0100, Mike Crowe wrote: As currently implemented, condition_variable always ultimately waits against std::chrono::system_clock. This clock can be changed in arbitrary ways by the user which may result in us waking up too early or too late when measured against the

[PATCH 1/2] condition_variable: Report early wakeup of wait_until as no_timeout

2018-07-10 Thread Mike Crowe
As currently implemented, condition_variable always ultimately waits against std::chrono::system_clock. This clock can be changed in arbitrary ways by the user which may result in us waking up too early or too late when measured against the caller-supplied clock. We can't (yet) do much about