for Reasons folks are talking about monotoic time again, and so it's time for me to link this comment again. https://github.com/rust-lang/rust/blob/e2223c94bf433fc38234d1303e88cbaf14755863/src/libstd/time.rs#L205-L232 …
-
Show this thread
-
Replying to @steveklabnik
As far as I know, QueryPerformanceCounter on Windows is expected to be monotonic (and is documented that way). It's possible that a hypervisor is doing something to invalidate this, but that would be a correctness issue in the hypervisor I believe. https://docs.microsoft.com/en-us/windows/win32/sysinfo/acquiring-high-resolution-time-stamps …pic.twitter.com/Mgh07XwINs
1 reply 0 retweets 1 like -
Replying to @epakskape
When real world users are experiencing panics because of an OS and/or hardware bug, saying "well use a platform without bugs or get them to fix it" isn't particularly helpful.
1 reply 0 retweets 3 likes -
Replying to @sgrif
That is not what I was saying :) I understand the need to work around things, I was just stating how the API is expected to behave.
1 reply 0 retweets 0 likes
Right, that's why it was implemented on top of that API in the first place. That's just not how it behaves in practice :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.