Consolidated reply to comments John Cowan (10 Nov 2019 05:32 UTC)
Fixnum range Lassi Kortela (11 Nov 2019 15:20 UTC)
Re: Fixnum range John Cowan (11 Nov 2019 17:15 UTC)
Re: Fixnum range John Cowan (12 Nov 2019 17:08 UTC)

Fixnum range Lassi Kortela 11 Nov 2019 15:20 UTC

> I also explained how an implementation may and may not use a fixnum check
> if the representation of a timestamp is not disjoint.

This comes in handy, but the current wording about the range of
timespecs is vague. IMHO we should either require a minimum range for
the seconds component (in bits) or require the implementation to
document its range (and to document whether or not it accepts a bignum
as the seconds component).