[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Exposing subsecond precision in current-seconds

From: felix . winkelmann
Subject: Re: Exposing subsecond precision in current-seconds
Date: Wed, 29 Apr 2020 16:34:17 +0200

> The trouble with procedure names of the form `current-*seconds` is that
> it's not clear whether they return an integer or a float. And in the
> case of a float, which subdivision of time is represented by the integer
> part.
> E.g. does `current-microseconds` return an integer number of
> microseconds, or does it return a float whose integer part is full
> seconds and the fractional part is partial seconds sourced from a
> roughly microsecond-precision timer? Same concern with
> `current-milliseconds` and `current-nanoseconds`.

I think it's straightforward: "current-*seconds" always returns an
integral value, which is both intuitive and efficient. No need to deal
with flonum fuckery more than necessary.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]