We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Examples:
julia> a = ([1,2,3], [4,5,6]) ([1,2,3],[4,5,6]) julia> [a...] WARNING: [a,b] concatenation is deprecated; use [a;b] instead in depwarn at ./deprecated.jl:40 in oldstyle_vcat_warning at ./abstractarray.jl:26 in vect at abstractarray.jl:29 6-element Array{Int64,1}: 1 2 3 4 5 6 julia> data_in = ("hello", 23, 2.7, (), [], (1,8)) ("hello",23,2.7,(),None[],(1,8)) julia> [data_in...] #missing [] from output 5-element Array{Any,1}: "hello" 23 2.7 () (1,8)
The deprecation warning is for v0.4, but v0.3 has the same behavior (minus the deprecation warning).
In hindsight, this could probably have been predicted from the current behavior... I just find it surprising.
Related: #10338 (and possibly can be absorbed there?)
Cc: @Jutho
The text was updated successfully, but these errors were encountered:
Presumably when [a, b] ceases to concatenate after the deprecation period (#8599), this won't concatenate either.
[a, b]
Sorry, something went wrong.
Presumably, yes. I'll close this then--it doesn't seem like it's affected anyone until now, and should be handled properly in 0.5 (or whenever).
No branches or pull requests
Examples:
The deprecation warning is for v0.4, but v0.3 has the same behavior (minus the deprecation warning).
In hindsight, this could probably have been predicted from the current behavior... I just find it surprising.
Related: #10338 (and possibly can be absorbed there?)
Cc: @Jutho
The text was updated successfully, but these errors were encountered: