On Wednesday, October 21, 2015 at 3:11:44 AM UTC-4, Gabriel Gellner wrote: > > I find the way that you need to use `linspace` and `range` objects a bit > jarring for when you want to write vectorized code, or when I want to pass > an array to a function that requires an Array. I get how nice the iterators > are when writing loops and that you can use `collect(iter)` to get a array > (and that it is possible to write polymorphic code that takes LinSpace > types and uses them like Arrays … but this hurts my small brain). But I > find I that I often want to write code that uses an actual array and having > to use `collect` all the time seems like a serious wart for an otherwise > stunning language for science. >
Ranges are actual arrays; they are subtypes of AbstractVector. Any vectorized operation in the standard library that works for Array but not for Range is probably a bug, because it won't work for other array types either.
