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 20, 2023. It is now read-only.
it would be more accurate to have calculation done on floating points at the 10 or 100 picoseconds level instead of relying on Double doing the right thing related to rounding. Some calculation might still require Double convertion, but some like (min, max... don't)
The text was updated successfully, but these errors were encountered:
I wrote a tiny package that uses Int64 for timestamps in nanoseconds (wraps hourglass to get nanosecond resolution timestamps from operating system, actually). You obviously don't need a dependency on my thing but fwiw Int64 works out nicely for this sort of application. https://hackage.haskell.org/package/chronologique fwiw
@ocramz oh, damn, sorry for the oversight. Thanks for pointing it out. Code is at https://github.com/afcowie/chronologique/. I just did a point release with the links added to the .cabal file.
it would be more accurate to have calculation done on floating points at the 10 or 100 picoseconds level instead of relying on
Double
doing the right thing related to rounding. Some calculation might still requireDouble
convertion, but some like (min, max... don't)The text was updated successfully, but these errors were encountered: