This is still an option but I'm yet to be convinced that we want to have that many things exported: linrange, LinRange, and linspace which just does collect on linrange? Seems like one too many.
On Sunday, October 25, 2015, Gabriel Gellner <[email protected]> wrote: > > > On Sunday, 25 October 2015 07:05:03 UTC-7, Christoph Ortner wrote: >> >> >> very nice example - thank you - but I notice that you use linrange :). >> >> Thanks, Christoph >> > > Man I wish they had called it linrange ;) with type LinRange. Still I am > at peace with the new way it works. Hopefully it will get faster in the > future, and with the upcoming printing changes I think it will become a > minor headache in corner cases at worst (in which case using collect will > be no problem). I don't think the python range/xrange is a good comparison > as that is a function that was almost always used for looping in that > language so of course the iterator is the best idea. linspace is often used > for array creation in languages like Matlab. > > Gabriel >
