Talk:cpp/chrono/high resolution clock

"the time between ticks is constant". Isn't this always true because member type already specifies seconds per tick?


 * What was meant time span between ticks might be very large or even negative in case the clock is adjusted when is_steady == false. I'll try to describe it in a more understandable way. P12 08:03, 22 December 2012 (PST)
 * so member type may fail to represent the real value of seconds per tick， if is_steady == false? 222.205.6.190 18:24, 22 December 2012 (PST)
 * Yes. P12 18:28, 22 December 2012 (PST)

Howard Hinnant (the author of chrono) has publicly stated that high_resolution_clock was a mistake: in real world implementations, internally it ends up just being either a steady_clock or system_clock... but it's inconsistent and the developer does not know which it is.

Perhaps we should note that on the page for it?

Hadriel (talk) 09:53, 12 December 2019 (PST)