- From: Philipp Dunkel <notifications@github.com>
- Date: Wed, 31 Oct 2018 09:05:16 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 31 October 2018 16:05:38 UTC
Re: DOMHighResTimeStamp/DOMTimeStamp Both of these are defined as floating point values representing milliseconds. That in turn means that while the resolution may be sufficient, the precision may be off. Again we have opted to be more explicit. * `Instant.prototype.seconds` - the number seconds since epoch * `Instant.prototype.milliseconds` - the number milliseconds since epoch * `Instant.prototype.microseconds` - the bigint microseconds since epoch * `Instant.prototype.nanoseconds` - the bigint nanoseconds since epoch Being explicit and using `BigInt` where relevant ensures that we have both resolution and precision to be correct for calculations. Using * `Instant.fromSeconds(seconds : number)` * `Instant.fromMilliseconds(milliseconds : number)` * `Instant.fromMicroseconds(microseconds : bigint)` * `Instant.fromNanoseconds(nanoseconds : bigint)` allows for interoperation. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/311#issuecomment-434742883
Received on Wednesday, 31 October 2018 16:05:38 UTC