Which CLOCK does `Temporal` API implementation use in a deno runtime?
How is the following
Details:
I'm writing an extternal process that uses
- On
- On
Below I've read the various clocks on
Notice
Notice only
The other clocks will drift from real time over time, and I may not get consistent readings in the
Question
How is the following
typescripttypescript line implemented in the denodeno runtime to get the nanonanoseconds from epoch, which system CLOCKCLOCK or SYSCALLSYSCALL does it use, is it possible for a denodeno contributor to point me towards the (rust?) source code for the implementation?Details:
I'm writing an extternal process that uses
ffiffi to integrate with a typescripttypescript process in a denodeno runtime. I want to get nanosecond-precision timestamps in my ffiffi process that are consistent with the timestamps in tsts. When I use REALTIMEREALTIME as the clock:- On
ubuntuubuntu I get nanonanoseconds from epoch resolution, and I'm good. :check: - On
macosxmacosx I get micromicroseconds from epoch resolution, and that's a problem. :no: Below I've read the various clocks on
macosxmacosx preceeded by their resolutions.Notice
.nsec.nsec field in the first resres line for a clock gives the resolution in nanoseconds, and the .sec.sec + .nsec.nsec fields in the second nownow line for a clock reading give the current time stamp for that clock.Notice only
REALTIMEREALTIME clock has the proper time since epoch, but has it in 10001000 .nsec.nsec => micromicrosecond resolution so returns 000000 for the last three digits of .nsec.nsec in the reading.The other clocks will drift from real time over time, and I may not get consistent readings in the
ffiffi process as in the denodeno typescript process.Question
How is the following
typescripttypescript line implemented in the denodeno runtime to get the nanonanoseconds from epoch, which system CLOCKCLOCK or SYSCALLSYSCALL does it use, is it possible for a denodeno contributor to point me towards the (rust?) source code for the implementation?
