Similar issue to #70, before? after? and equal? for goog.date.Date are implemented in terms of .getTime.
(ct/before? (ct/today) (ct/today)) => true
So I was going to submit a pull request, with different implementations of those, using the same methods as were used in #70. but then I was thinking if cljs-time.extend wasn't optional then the impl would be a bit simpler. I guess you have good reason for it being optional, but wanted to check first
Similar issue to #70, before? after? and equal? for goog.date.Date are implemented in terms of .getTime.
(ct/before? (ct/today) (ct/today))
=> trueSo I was going to submit a pull request, with different implementations of those, using the same methods as were used in #70. but then I was thinking if
cljs-time.extend
wasn't optional then the impl would be a bit simpler. I guess you have good reason for it being optional, but wanted to check first