The following line doesn’t error but doesn’t have any affect on b2 b2[vec(b2)][ p2[xhalt*2:end] ] .= false; Working in the same scope: b3 = @view b2[vec(b2)]; b3[ p2[rmax+1:end] ] .= false; b2 is a bitvector, p2 a vector of ints Repeatable b2 = trues(50); p2 = randperm(50); b2[b2][p2[20:end]] …

[image] y4lu: So, is the current behaviour intended? Yes. [image] y4lu: behaviours of get/setindex on the left hand side. So you mean getindex and setindex! should behave the same? I can take a few guesses why you might think that way (if they are wrong, please ignore…): If you are …

MWE - setindex bug?

General Usage

Tamas_Papp November 26, 2018, 3:19pm 2

Please provide a self-contained MWE, with b2 etc defined.

2 Likes

Topic		Replies	Views
Setting array values through sequential application of two sets of indices General Usage	2	412	July 30, 2018
Indexing vectors wtih BitVectors General Usage	3	70	October 31, 2024
Surprising dot broadcast result when indices are repeated? General Usage question , indexing , broadcast , arrays	9	491	May 13, 2021
Strange logical indexing behavior with 3-dimensional Array and BitMatrix General Usage indexing , array	3	243	November 14, 2023
Error reported in a blank line (MethodError: no method matching getindex(::Float64, ::UnitRange{Int64}) General Usage question	5	399	February 18, 2020

MWE - setindex bug?

Related topics