Date: Thu, 26 Dec 2019 16:52:12 +0900
2019年12月22日(日) 2:18 Thiago Macieira via Std-Proposals <
std-proposals_at_[hidden]>:
> On Saturday, 21 December 2019 05:42:44 PST Andrey Semashev via
> Std-Proposals
> wrote:
> > Time points and durations, at least from the system and steady clocks,
> > are not intended to be used for representing calendar dates, especially
> > not in the far past or future. One of their main use cases is relatively
> > short term timed operations (e.g. various timeouts, operation intervals
> > and scheduling, etc.), meaning that magnitute orders of sub-seconds to
> > seconds are much more prevalent than hours, days or even years. These
> > clocks and associated time points and durations are designed to be
> > efficient for that use case. Choosing e.g. a larger representation type
> > to increase the range would add unneeded performance overhead.
>
Thanks a lot.
I understand chrono design and purpose.
std-proposals_at_[hidden]>:
> On Saturday, 21 December 2019 05:42:44 PST Andrey Semashev via
> Std-Proposals
> wrote:
> > Time points and durations, at least from the system and steady clocks,
> > are not intended to be used for representing calendar dates, especially
> > not in the far past or future. One of their main use cases is relatively
> > short term timed operations (e.g. various timeouts, operation intervals
> > and scheduling, etc.), meaning that magnitute orders of sub-seconds to
> > seconds are much more prevalent than hours, days or even years. These
> > clocks and associated time points and durations are designed to be
> > efficient for that use case. Choosing e.g. a larger representation type
> > to increase the range would add unneeded performance overhead.
>
Thanks a lot.
I understand chrono design and purpose.
Received on 2019-12-26 01:54:52