Closed qgeissmann closed 5 years ago
I'd rather be explicit here, and not coerce implicitly.
Seems we can't define Ops.hms()
without breaking things (#18). Would we need that to change the behavior of >
?
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 writingx > "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