The major change that has already happened is that singleton slices are
dropped regardless of whether they are trailing or not. Thus, both column
and row slices return vectors:
julia> A = rand(3,4)
3x4 Array{Float64,2}:
0.901849 0.928557 0.234609 0.0242837
0.639919 0.434856 0.735784 0.890218
0.592287 0.830999 0.579136 0.917481
julia> A[1,:]
4-element Array{Float64,1}:
0.901849
0.928557
0.234609
0.0242837
julia> A[:,1]
3-element Array{Float64,1}:
0.901849
0.639919
0.592287
What has not yet changed and has recently had a renewed round of debate is
the change from array slices returning copies by default to potentially
returning views by default. There are a few other changes that are planned,
but they won't break code that doesn't currently have any deprecations on
master.
On Tue, Feb 2, 2016 at 4:21 AM, Mauro <[email protected]> wrote:
> > What is the arraypocalypse?
>
> Braking changes for array indexing are on the plate for 0.5:
> https://github.com/JuliaLang/julia/issues/13157
>
> Note that another name is arraymageddon:
>
> https://github.com/JuliaLang/julia/search?utf8=%E2%9C%93&q=arraymageddon&type=Issues
>
>
> The terms stems from the previous tupocalypse, when a tuple-type
> overhaul lead to a few breakages:
>
> https://github.com/JuliaLang/julia/search?utf8=%E2%9C%93&q=tupocalypse&type=Issues
>
> https://github.com/JuliaLang/julia/search?q=tupocolypse&type=Issues&utf8=%E2%9C%93
>
>
> > On Tuesday, February 2, 2016 at 1:28:26 AM UTC-5, Mauro wrote:
> >>
> >> > my tests run smoothly in the current build of julia 0.5 beta. Is
> >> everything
> >> > good or are there breaking changes to come?
> >>
> >> There are always breaking changes to come on Master... that's the point
> >> of Master. Expect more to come, as the arraypocalypse has not happened
> >> yet (nor it is quite clear how it will happen).
> >>
>
