-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow dropping of fractional time parts and relax a bit parsing syntax #51
Comments
All good. Plus flexibility on input ie recognise
and so on. |
We allow To get the ball rolling for an exhaustive specification when the input is
Hopefully this makes the handling of |
That reads well. Some quick comments:
Yay to having specs. I feel like a grown-up now. |
0: absolutely, and I think we already have it working right now: nanotime(12345L)
[1] "1970-01-01T00:00:00.000012345+00:00" For output, unconditional long displays would occur if the user specifies a format. But alternatively, we could have another environment variable that controls this feature. Still think it should be on by default, as it really helps visually and the hope is that |
It would be nice to allow, amongst others:
In output, the fractional time and parts could be omitted when no element of the vector to be printed has fractional part. Again this would be like
POSIXct
.Finally, in output, the default prints out the time zone offset, but the timezone abbreviation is shorter and would be the same as
POSIXct
:This saves one to two characters per printout.
Finally, besides the missing 'T', there could also be forgiveness for using '/' or '' instead of '-' as date separator?
The text was updated successfully, but these errors were encountered: