[julia-users] Why does the warning go away? (Or: my first Julia WAT)

2016-03-29 Thread Manor Askenazi
# So, ranges are a thing: julia> 1:3 1:3 # Not an obvious type, but OK: julia> typeof(1:3) UnitRange{Int64} # And they can be assigned to variable, good. julia> a = 1:3 1:3 # WAT: A warning about using collect()? julia> a = [1:3] WARNING: [a] concatenation is deprecated; use collect(a) inste

Re: [julia-users] Why does the warning go away? (Or: my first Julia WAT)

2016-05-03 Thread Manor Askenazi
> > > I am not sure what the question is about {}. It has been deprecated so > that it can be freed for new syntax. See > https://github.com/JuliaLang/julia/pull/10380 > > Best, > > Tamas I was contrasting the behavior of the warning system, which "gave up" after three warnings in the fir

Re: [julia-users] Why does the warning go away? (Or: my first Julia WAT)

2016-03-29 Thread Tamas Papp
Even though experimenting with the command line is an important part of learning a about language, you can usually figure out conceptual features better from reading the documentation. In particular, release notes inform about deprecations. [...] was used frequently to convert to a vector, but it

Re: [julia-users] Why does the warning go away? (Or: my first Julia WAT)

2016-03-29 Thread Mauro
> # WAT: A warning about using collect()? > > julia> a = [1:3] > WARNING: [a] concatenation is deprecated; use collect(a) instead > in depwarn at deprecated.jl:73 > in oldstyle_vcat_warning at > /Applications/Julia-0.4.5.app/Contents/Resources/julia/lib/julia/sys.dylib > in vect at abstractarray