You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hit this issue while doing a test of QuantEcon.jl which passes fine in Julia 0.4.6 but fails in 0.6 current.
From QuantEcon:
Testing markov_approx.jl: Error During Test
Got an exception of type ErrorException outside of a @test
indexed assignment not defined for LinSpace{Float64}
in copy!(::LinSpace{Float64}, ::LinSpace{Float64}) at ./multidimensional.jl:614
in tauchen(::Int64, ::Float64, ::Float64, ::Float64, ::Int64) at /home/colin/.julia/v0.6/QuantEcon/src/markov/markov_approx.jl:76
in macro expansion; at /home/colin/.julia/v0.6/QuantEcon/test/test_markov_approx.jl:15 [inlined]
Since this is related to copy! I ran a test
a = linspace(1,4,3)
b = linspace(1,4,3)
copy!(b,a)
ERROR: indexed assignment not defined for LinSpace{Float64}
in copy!(::LinSpace{Float64}, ::LinSpace{Float64}) at ./multidimensional.jl:614
And the same happens for range objects but is fine for arrays.
It seems reasonable that copy should be defined at least for linspace, so I'm starting the report here, but can move elsewhere if advised.
versioninfo()
Julia Version 0.6.0-dev.488
Commit 79a7172* (2016-09-05 06:23 UTC)
Platform Info:
System: Linux (x86_64-suse-linux)
CPU: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz
WORD_SIZE: 64
BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Haswell)
LAPACK: libopenblas64_
LIBM: libopenlibm
LLVM: libLLVM-3.7.1 (ORCJIT, haswell)
The text was updated successfully, but these errors were encountered:
Hit this issue while doing a test of QuantEcon.jl which passes fine in Julia 0.4.6 but fails in 0.6 current.
From QuantEcon:
Since this is related to copy! I ran a test
And the same happens for range objects but is fine for arrays.
It seems reasonable that copy should be defined at least for linspace, so I'm starting the report here, but can move elsewhere if advised.
The text was updated successfully, but these errors were encountered: