Skip to content

Conversation

JeffBezanson
Copy link
Member

fix #45825

@JeffBezanson JeffBezanson added arrays [a, r, r, a, y, s] bugfix This change fixes an existing bug labels Jun 27, 2022
@vchuravy vchuravy added backport 1.6 Change should be backported to release-1.6 backport 1.7 backport 1.8 Change should be backported to release-1.8 labels Jun 27, 2022
@martinholters
Copy link
Member

Might be too breaking before 2.0, but shouldn't BitArray(::OffsetArray) throw just like Array{Bool}(::OffsetArray) does (unless the start index happens to be 1)?

@JeffBezanson
Copy link
Member Author

Oh I see, I was just wrong about what behavior is intended then. I was thinking of the argument as an iterator.

@JeffBezanson
Copy link
Member Author

Ok this should be right now. Using nextind seems to give full performance.

@JeffBezanson JeffBezanson merged commit 820c08b into master Jul 18, 2022
@JeffBezanson JeffBezanson deleted the jb/fix45825 branch July 18, 2022 19:02
KristofferC pushed a commit that referenced this pull request Jul 20, 2022
@KristofferC KristofferC removed the backport 1.8 Change should be backported to release-1.8 label Aug 7, 2022
ffucci pushed a commit to ffucci/julia that referenced this pull request Aug 11, 2022
pcjentsch pushed a commit to pcjentsch/julia that referenced this pull request Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arrays [a, r, r, a, y, s] backport 1.6 Change should be backported to release-1.6 bugfix This change fixes an existing bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BitArray "constructor" incorrectly assumes 1-based indexing, leading to nondeterministic incorrect results due to out-of-bounds memory access
5 participants