milktrader

By all means make a PR to the float_time branch. It would be easier to see the code to make comments. Github also has a feature where comments can be...

Agreed on how human's view time! I'm not planning to merge the float_time branch anytime soon. There is benchmarking, documentation, and a boatload of tests that would be required. I...

Wondering how to close this and think maybe we can add in the documentation that this branch exists. Also, who has the git-fu for continuing to update the branch with...

@dourouc05 can you provide a reproducible example (preferably using MarketData), to demonstrate your objective. It seems to me you just want a change in the API but I might not...

I think I get the gist of your point @dourouc05 and I've changed the title of the issue. Please comment on the change.

I don't know offhand but how does Base.Dates handle irregular intervals (I know it does). The second argument in the `collapse` method should be able to take this as a...

Here is an example of one could get to 2-day intervals ``` julia julia> first(cl.timestamp):Day(2):last(cl.timestamp); julia> cl[collect(ans)] 253x1 TimeSeries.TimeArray{Float64,1,Date,Array{Float64,1}} 2000-01-03 to 2001-12-31 Close 2000-01-03 | 111.94 2000-01-05 | 104.0 2000-01-07...

@quinnj what type would you dispatch on given that `Day(2)` is a `Base.Dates.Day`? Once we figure out that piece of the puzzle, we simply write a method that takes that...

``` julia julia> bar = first(cl.timestamp):Day(2):last(cl.timestamp) 2000-01-03:2 days:2001-12-31 julia> isa(bar, StepRange) true ```

@dourouc05 when you want a user-defined range, let's say 2-day interval, does that mean two calendar days or the last two observations of a TimeArray?