My main objection is that changing the behaviour of linspace is superfluous considering linrange already existed. If the goal was to encourage users to use a range instead of an array that should of been done through documentation through something like a best practices section (e.g. Use linrange instead of linspace).
On Wednesday, September 30, 2015 at 12:27:02 PM UTC-7, Matt Bauman wrote: > > There can be reasons where a special read-only `Ones` array type is > beneficial: http://stackoverflow.com/a/30968709/176071. It's just five > lines of code, and Julia/LLVM is able to optimize it such that > multiplication is totally elided. It's pretty cool. But as others said, > these functions are fairly well entrenched in creating mutable arrays. The > output from linspace, however, isn't typically mutated. > > Back to linspace, I'm still curious to hear more reasons for the strong > dislike. Is it because of how it behaves? Or how it performs? Or how > it's displayed (which is also valid)? >
