News for hackers. Stuff that matters.
Re:Julia's Arraypocalypse Release by StefanKarpinski on Sunday September 27, 2015 @04:34PM (#10287870)
Totally different typical usage patterns. Taking substrings and throwing away the original string is the norm for text. Taking a column of a matrix and throwing away the original matrix is not. Different domains call for different design tradeoffs – this change stems from extensive practical experience with writing numerical algorithms.
Re:Julia's Arraypocalypse Release by masklinn on Monday September 28, 2015 @04:06AM (#10289357)
Note that I am not saying it's a bad default (it still is the default of Erlang binaries).

I am saying this change is not quite "just a matter of performance", that the documentation and changelogs should be very very clear about the behavioural changes and the possible issues with the new behaviour, and that there should be an easy way to "unshare" slices and force a copy.

Re:Julia's Arraypocalypse Release by lqdc13 on Sunday September 27, 2015 @05:27PM (#10287991)
would there still be an easy way to make copies?

Like advanced indexing (http://docs.scipy.org/doc/numpy/reference/arrays.indexing.ht...) in the Python world?

Re:Julia's Arraypocalypse Release by elcritch on Monday September 28, 2015 @12:35AM (#10288930)
You could just use a list comprehension, e.g. `[ x for x in arrayveiw1 ]` or perhaps a copy function will be added to Base.
Re:Julia's Arraypocalypse Release by StefanKarpinski on Monday September 28, 2015 @10:43AM (#10290695)
There's already a copy function that does this.
Re:Julia's Arraypocalypse Release by elcritch on Tuesday September 29, 2015 @04:47PM (#10299515)
Great, Julia seems to have a good assortment of those "I need XYZ" (for scientific programming) and it's already in Base. I should check the apropos more.