Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
get-internal-real-time should return monotonic time #20
which a non-monotonic clock is not. Proposed solution: have
I am not against having
Linux, FreeBSD, and Solaris-ish systems have
The Macintosh has
For Windows, there's
https://www.python.org/dev/peps/pep-0418/ collects a lot information about various systems.
According to PEP 418 / Operating system time functions / Monotonic Clocks the options you mentioned all do include sleep (but only the proposed windows API accounts for time spent suspended—not sure if this is desired). Its looks though, as if
Disclaimer: I am absolutely clueless of windows APIs.
but I am afraid I would be no help at all with the windows implementation of
I made it sound like
The standard is also kind of vague about requirements for internal time
While I find the reference to clock time confusing, I tend to interpret “elapsed real time” to mean it should be monotonic.
So let’s say I want to fix this: I noticed hat
Certainly stuff in
There are or were certain restrictions about using
I'd try moving the definition of
Let me take a step back and question my own agenda here. I’ve looked at the sources of two other open source implementations (SBCL and ECL) and neither implement
While I think that my interpretation of
Most importantly it would relieve implementations from bothering about it. I.e. if I had my way and CCL’s
Whether or not that overhead is worth it depends on the CCL users. Does anyone except me want this behavior? It might be a net-positive for CCL to have this feature, regardless of what other implementations do. It might also be that everyone is better off if I try to contribute to @death’s monotonic-clock library instead.