A fresh major release of the nanotime package for working with nanosecond timestamps is hitting CRAN mirrors right now.
nanotime relies on the RcppCCTZ package for (efficient) high(er) resolution time parsing and formatting up to nanosecond resolution, and the bit64 package for the actual
integer64 arithmetic. Initially implemented using the S3 system, it has benefitted greatly from work by Leonardo Silvestri who rejigged internals in S4—and now added new types for periods, intervals and durations. This is what is commonly called a big fucking deal!! So a really REALLY big thank you to my coauthor Leonardo for all these contributions.
With all these Yuge changes patiently chisseled in by Leonardo, it took some time since the last release and a few more things piled up. Matt Dowle corrected something we borked for integration with the lovely and irreplacable data.table. We also switched to the awesome yet minimal tinytest package by Mark van der Loo, and last but not least we added the beginnings of a proper vignette—currently at nine pages but far from complete.
The NEWS snippet adds full details.
Changes in version 0.3.0 (2020-08-06)
tz=in call to RcppCCTZ::parseDouble()) (Matt Dowle in #49).
Add new comparison operators for
charcters(Dirk in #54 fixing #52).
Switch from RUnit to tinytest (Dirk in #55)
Substantial functionality extension in with new types
nanoperiod(Leonardo in #58, #60, #62, #63, #65, #67, #70 fixing #47, #51, #57, #61, #64 with assistance from Dirk).
A new (yet still draft-ish) vignette was added describing the four core types (Leonardo and Dirk in #71).
A required compilation flag for Windows was added (Leonardo in #72).
RcppCCTZ function are called in new 'non-throwing' variants to not trigger exeception errors (Leonardo in #73).
We also have a diff to the previous version thanks to CRANberries. More details and examples are at the nanotime page; code, issue tickets etc at the GitHub repository.
If you like this or other open-source work I do, you can now sponsor me at GitHub. For the first year, GitHub will match your contributions.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.