His near brush with death changed his mindset completely.
Berserk Button: Do not mention it must be great to be a Sawatari child to him or call him a "virgin".He can turn back time with the pocket watch he received from his late grandfather. Any kind of further insight on this disparity, or examples of where this could cause problems would be much appreciated.The protagonist and the oldest son of the Sawatari family who is next in line to inherit their company. My question is, after having used std::chrono::high_resolution_clock for so many years (for frame timers and benchmarks), should I be more concerned than I am? Even here on this site, I see many recommendations to use std::chrono::high_resolution_clock, despite what this footnote says. but isn't this true for std::chrono::steady_clock and std::chrono::system_clock as well? For instance, I was unable to find anything that guaranteed that the clock periods between clocks must be in certain units. Their rationale was that the clock varies by implementation. Notice that cppreference explicitly discourages the use of std::chrono::high_resolution_clock.
Recently, I stumbled across a footnote here: This is not necessarily true for libstdc++ and libc++, hence the use of the alias. Therefore, on MSVC, the alias I have defined will just use std::chrono::steady_clock.
Note that MSVC currently uses the following alias to define std::chrono::high_resolution_clock: using high_resolution_clock = steady_clock In other words, I want a clock that is defined using the highest possible resolution, but it must increment monotonically. I have been using the following clock definition for a frame timer for years now: using frame_clock = std::conditional_t
0 kommentar(er)
