Ranges made from `CFTime` Period can have floating point length

[rafaqz]

length should really always be an Int to follow the AbstractArray interface... something is going wrong.

using CFTime , Dates
import CFTime: Period

# A DateTime360Day backed by a Float64 Period (which is what NCDatasets
# produces when reading a CF time variable from a 360-day-calendar netCDF file).
P  = Period{Float64, Val{86400}(), Val{0}()}      # 1-day unit, Float64-backed
DT = DateTime360Day{P, Val{(2001, 1, 1)}()}

start = DT(P(0.0))
stop  = DT(P(86400.0 * 23))
step_ = P(86400.0)
r = start:step_:stop
length(r)

Output:

24.0

Version:

(tmp) pkg> status
Status `/tmp/Project.toml`
  [179af706] CFTime v0.2.9

[rafaqz]

Note this breaks generic Base ranges usually returned from axes like Base.OneTo, that only accept Int.

[Alexander-Barth]

Thank you for reporting. This should be fixed now.