i.e. we hit the immutable version. This is a bug in the current possible implementation for BangBang._setindex!, which only checks that the eltype is valid; in the above case, the eltype(x) is of course Float64 but the element provided x[:, 1] is of type Vector{Float64}, hence it fails.
Currently, we have the following behavior:
i.e. we hit the immutable version. This is a bug in the current
possible
implementation forBangBang._setindex!
, which only checks that theeltype
is valid; in the above case, theeltype(x)
is of courseFloat64
but the element providedx[:, 1]
is of typeVector{Float64}
, hence it fails.In this PR, we have
as desired.