I was expecting this ticket to yield some statement about the design
objectives of Instant.from-posix() and the related leap second code,
but that hasn't happened yet, and it's beginning to look as though there
isn't any firm objective. So I think it might be helpful to lay out
the problem space.
zof...@zoffix.com wrote:
>Perhaps, we should evaluate some of the leap-second estimation algorithms.
If you like. To be clear, I'm not pushing for the conversion to use an
estimation strategy per se, and we're now going beyond what's necessary
to address my original bug report. Documenting the e
Perhaps, we should evaluate some of the leap-second estimation
algorithms. There are
more leap second problems in Rakudo besides the .from-posix, that I
now opened in
https://rt.perl.org/Ticket/Display.html?id=128752
Quoting Zefram :
Zoffix Znet via RT wrote:
Returning zero is much more
Zoffix Znet via RT wrote:
>Returning zero is much more predictable than returning a guess,
The case where the algorithm is operating in its unknown-future regime is
not as easily spotted as that. The return value from the conversion is
not a fixed value, it's a value that is well-formed and valid
Zoffix Znet via RT wrote:
>This means the result of the code is dependent on the version of the
>compiler and is thus inherently unpredictable, **even for historical
>values.**
Absolutely right that the `future' behaviour also applies to times that
are actually in the past, when running on an old
