You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 18, 2023. It is now read-only.
In this way, the user can remain ignorant of the fact that Millisecond is the best unit to divide an interval (so that if/when DateTime starts to include microseconds, the user doesn't have to change her code).
Or perhaps we want to create a FloatingpointMillisecond type which would be to Millisecond what Float64 is to Int?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I may well be missing something but it seems that currently you can't do this:
I need to do this a lot to interpolate times. As far as I can tell, the following is the only robust way to do it:
I know the integer division (÷) works, but it doesn't do rounding.
Intervals behave like an integer, but for the actual integer, the following method is standard:
This works because Int/Int results in Float64.
This discussion suggests that we perhaps need a special division function:
In this way, the user can remain ignorant of the fact that Millisecond is the best unit to divide an interval (so that if/when DateTime starts to include microseconds, the user doesn't have to change her code).
Or perhaps we want to create a
FloatingpointMillisecond
type which would be to Millisecond what Float64 is to Int?The text was updated successfully, but these errors were encountered: