Open yha opened 3 years ago
Thanks for reporting this bug. At first it seemed pretty esoteric to me. I have to admit that I don't understand broadcasting very much. I looks like somehow broadcasting is throwing a Base.Broadcast.Extruded
into the situation, I have no idea what that is supposed to do. Maybe @diegozea knows what is going on?
Idk if this is related, but I think I was able to reproduce the error when I forgot to specify the type parameter for an array (any kind really) before operating on it. For example:
n = NamedArray(zeros(Complex, 2))
n .- 2
throws the BoundsError
above, while:
n = NamedArray(zeros(Complex{Float64}, 2))
n .- 2
looks to behave as expected
Thanks, pretty esoteric indeed. Thanks for finding this one
A simple reproducer:
I encountered this when trying to work with block arrays with named blocks, roughly as follows: