Re:Jiff: A brand new Datetime library for Rust, from the aut...
by burntsushi on Monday July 22, 2024 @05:26PM
(#41039999)
The components are stored separately. I think what you are advocating for is component wise addition, which I mentioned in my previous comment. It can totally "work," but as I said, it will produce different results than `span1.checked_add(span2)`. For example:
use jiff::{ToSpan, Unit, Zoned};
fn main() -> anyhow::Result<()> {
let span1 = 1.year().months(3);
let span2 = 11.months();
let now = Zoned::now().round(Unit::Minute)?;
let added = span1.checked_add((span2, &now))?;
println!("{added}");
Ok(())
}
Has this output: $ cargo -q r
P2y2m
Notice how the months overflow automatically into years. Days will do the same into months. You need a reference point to do this correctly. For example, just `span1.checked_add(span2)?` would produce an error.In contrast, component wise addition would lead to a span of `1 year 14 months`. Which is a valid `Span`. Jiff is fine with it. But it's different than what `checked_add` does. Having both operations seems too subtle.
Also, I don't really think using the `+` operator just to construct spans is that much of a win over what Jiff already has. So that needs to be taken into account as well.
Re:Jiff: A brand new Datetime library for Rust, from the aut...
by Tobu on Tuesday July 23, 2024 @05:12AM
(#41044135)
The Into<SpanArithmetic> argument feels a little too magical.
Since you are not constrained by a trait, I would prefer something like
Span::add_with_reference(&self, other: &Span, reference: impl Into<SpanRelativeTo>)
I'm thinking something along the lines of how ActiveSupport::Duration works:
Of course the downside being that it would need to be sized large enough to contain each component, even though they may be rarely used.