milktrader

It's more of a stretch to say values are a value than it it to say a timestamp is timestamps so I would vote for going plural. `timestamp` -> `timestamps`...

Also fwiw, the original names come from the name of the type parameters. `ts.values` `ts.timestamp`

After thinking about this for a few days I'm not sure we need to change the `timestamp` method name to `timestamps`. Here is my reasoning. `timestamp` is a field of...

I don't think so but if you find Query.jl supports TimeArrays please advise with an example.

The current behavior is missing values on dates in a single time series are simply not part of the `TimeArray`. When combining separate `TimeArrays`, if there is a value in...

I'm with @GordStephen on this. I think this functionality would be better suited for a completely different type than `TimeArray`. If you want to experiment, you could change the `timestamp`...

@ExpandingMan have you tried tweaking the existing type yet? I'd be interested to see what this looks like. I'd also be happy to make it a branch for this repo.

I changed like 7 lines of code to get this behavior ... ````julia julia> TimeArray(collect(1:10.), collect(1:10)) 10x1 TimeSeries.TimeArray{Int64,1,Float64,Array{Int64,1}} 1.0 to 10.0 1.0 | 1 2.0 | 2 3.0 | 3...

Appears this small change is actually pretty robust at first pass ... ````julia julia> foo = TimeArray(collect(1:10.), collect(1:10)); julia> bar = TimeArray(collect(1:10.), collect(101:110)); julia> head(foo) 1x1 TimeSeries.TimeArray{Int64,2,Float64,Array{Int64,2}} 1.0 to 1.0...

I just pushed the `float_time` branch. You should be able to checkout the branch and give it a try.