-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mysterious assertion failure when reinterpreting subarrays #7897
Comments
I fixed the assertion failure (not pushed yet though), but I'm wondering what reinterpret on a subarray should do. Opinions @JeffBezanson @StefanKarpinski? |
I think it's reasonable to just plain disallow that for now (it would be really really nice if we could reinterpret subarrays or array views, or whatever you want to call that though). I opened this issue because of the strange failure though. |
Alright, I'll fix the assertion failure and we can discuss subarray reinterpret later. |
What is the status of SubArray reinterpretation? If regular array views (x[a:b]) start being treated this way, it will be a regular occurrence. |
It seems fairly likely that this will be doable, but I haven't really thought about it seriously yet. |
In my naive attempts to chase the performance rabbit, I came across this interesting case:
This causes the following assertion failure:
Surprisingly, if I comment out the
a = data[1]
line, I get something much more sane:And it's not the fact that it's trying to read in from
data
that's confusing it; it's the fact that there is an array read at all; it could be a completely different array, and Julia still throws a hissy fit:The text was updated successfully, but these errors were encountered: