Open jakemanger opened 10 months ago
Agreed. Intervals are not exactly comparable, so comparison operations don't make sense and ==
is a special case of those.
Two options, either implement comparison operations as a partial order or, alternatively, error on all comparisons.
@vspinu I believe the comparison as a partial order approach would be much more useful (at least for me). I've implemented a proposed solution here #1136
If you attempt to use an
==
check with lubridate intervals, it uses the interval duration, rather than the interval object itself.Reading the docs for lubridate::interval, this doesn't seem like this should be the default behaviour. Shouldn't this act like comparing two time ranges?
Note, I am using lubridate 1.9.2