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
I personally find it quite useful to be able to implicitly coerce strings to time objects.
I believe this is implemented in POSIXct. For instance: as.POSIXct("2016-01-01") == "2016-01-01" is TRUE.
In hms, we could be writing x > "23:50:21.100" instead of x > hms(21.100, 50,23) (or explicitly using as.hms()).
Now, we have:
> hms(1) >"00:00:02"#> TRUE
I am happy to implement this new feature if you want
The text was updated successfully, but these errors were encountered:
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary.
I personally find it quite useful to be able to implicitly coerce strings to time objects.
I believe this is implemented in POSIXct. For instance:
as.POSIXct("2016-01-01") == "2016-01-01"
isTRUE
.In hms, we could be writing
x > "23:50:21.100"
instead ofx > hms(21.100, 50,23)
(or explicitly usingas.hms()
).Now, we have:
I am happy to implement this new feature if you want
The text was updated successfully, but these errors were encountered: