A finisher to an old issue about nanotime

[joshuaulrich]

This is related to floating point precision, and has nothing to do with nanotime. What Every Computer Scientist Should Know About Floating-Point Arithmetic provides a lot of background for why this is an issue and how to work around it.

Your precision never existed, even before you called nanotime():

1531830678123456789
# [1] 1.531831e+18
sprintf("%f", 1531830678123456789)
# [1] "1531830678123456768.000000"

And this works:

nanotime(bit64::as.integer64("1531830678123456789"))
[1] "2018-07-17T12:31:18.123456789+00:00"

[wsrfad]

Exactly ! That's why I was using time in character and then passing to nanotime. But eddelbuettel is hell bent on telling me that I do not do my homework ! Plz neither underestimate nor ridicule the feedback givers

[eddelbuettel]

@wsrfad One more time-wasting issue like this and I will block you. This serves as a warning. Your call.