[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 18:21:12 +0200 |
> On Wed, Apr 29, 2020 at 05:36:10PM +0200, address@hidden wrote:
> > > One thing I'm concerned about is that there's current-milliseconds, which
> > > returns the milliseconds since startup, while we'd have current-seconds
> > > and current-microseconds which return the (micro)seconds since the Epoch.
> > >
> >
> > Microseconds since epoch? Are you sure about this?
>
> What else would the new current-microseconds return?
Since startup, or since some undefined point of time. I see no sense in using
an absolute basetime, as such a timing command will in nearly all use cases
be used for relative timing. One should also attempt to reduce the range to
avoid bignum allocation, I think.
felix
- Re: Exposing subsecond precision in current-seconds, (continued)
- Re: Exposing subsecond precision in current-seconds, felix . winkelmann, 2020/04/27
- Re: Exposing subsecond precision in current-seconds, felix . winkelmann, 2020/04/29
- Re: Exposing subsecond precision in current-seconds, Peter Bex, 2020/04/29
- Re: Exposing subsecond precision in current-seconds,
felix . winkelmann <=
- Re: Exposing subsecond precision in current-seconds, Lassi Kortela, 2020/04/29
- Re: Exposing subsecond precision in current-seconds, Peter Bex, 2020/04/29
- Re: Exposing subsecond precision in current-seconds, felix . winkelmann, 2020/04/29
- Re: Exposing subsecond precision in current-seconds, Peter Bex, 2020/04/29
- Re: Exposing subsecond precision in current-seconds, felix . winkelmann, 2020/04/29
- Re: Exposing subsecond precision in current-seconds, Peter Bex, 2020/04/30
- Re: Exposing subsecond precision in current-seconds, felix . winkelmann, 2020/04/30