Curtis Vogt
Curtis Vogt
We could also support rounding for non-Period types
Ok, I expect I'll close this. I'll leave it open for now as things change around this.
The current commit switches `AnchorInterval{P, T}` to `AnchorInterval{T, P}` in preparation for additional commits which end up changing `AnchorInterval` to its final form of `AnchorInterval{T, S, E}` where `S` is...
Currently the `span` can field can be positive/negative which is strange as the `span` accessor only returns a positive value. I believe the code can be simplified if we restrict...
Note that with these changes since the value of the span is no longer part of the type things like `HourEnding` have spans of `Hour` but not necessarily one hour:...
Fair enough. I would like to get this merge next week sometime so let me know if you want to go through it together.
Fixes: https://github.com/invenia/Intervals.jl/issues/73
I have some additional ideas regarding `isless` and `Interval`s I want to explore.
I'm looking into alternative approaches. I think we may be able to fix Base code such the `+` and `-` invalidations no longer occur (see https://github.com/invenia/Intervals.jl/issues/144). As for converting to...
I think your floating-point interval example would be contiguous. This does mean we would be using the internal representation rather for this behaviour.