v0.2.6
Bug fixes
v0.2.5 introduces a major inconsistency, not just in its behavior for PrimitiveDateTime::using_offset
, but also changes its signature, rendering it incapable of being used in const
contexts.
Both the behavior and the function signature have been fixed, while still fixing the underlying issue. PrimitiveDateTime::using_offset
mentions in the docs that the PrimitiveDateTime
is assumed to be UTC, and is converted to the provided offset. This was the previous behavior.
The following functionality had bugs that were fixed (from v0.2.4):
OffsetDateTime::timestamp
OffsetDateTime::parse
- Equality, comparison for
OffsetDateTime
— Subsecond values were not checked previously. They also relied on the faulty timestamp implementation. - Hashing of
OffsetDateTime
— Same as equality and comparison. Additionally, hashes would collide withPrimitiveDateTime
if the underlying UTC was the same. - Subtraction of two
OffsetDateTime
s previously disregarded the subsecond values.
All of these changes are now checked in CI, so regressions will be caught.