For me, I think I just expect a vector from experience, and I could
probably just change the way I work with a little effort.
One exception (I think) is that I often do numerical integration over a
range of values, and I need the results at every value. I'm not sure if
there's a way to do that with range objects only.
On Tue, Sep 29, 2015, 20:59 Stefan Karpinski <ste...@karpinski.org> wrote:
> I'm curious why you need a vector rather than an object. Do you mutate it
> after creating it? Having linspace return an object instead of a vector was
> a bit of a unclear judgement call so getting feedback would be good.
>
> On Tuesday, September 29, 2015, Patrick Kofod Mogensen <
> patrick.mogen...@gmail.com> wrote:
>
>> No:
>>
>> julia> logspace(0,3,5)
>> 5-element Array{Float64,1}:
>> 1.0
>> 5.62341
>> 31.6228
>> 177.828
>> 1000.0
>>
>> On Tuesday, September 29, 2015 at 8:50:47 PM UTC-4, Luke Stagner wrote:
>>>
>>> Thats interesting. Does logspace also return a range?
>>>
>>> On Tuesday, September 29, 2015 at 5:43:28 PM UTC-7, Chris wrote:
>>>>
>>>> In 0.4 the linspace function returns a range object, and you need to
>>>> use collect() to expand it. I'm also interested in nicer syntax.
>>>
>>>
