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
Should indexing return copies? #38
Comments
Yes, I've had the same thought. Let's do that. |
timholy
added a commit
that referenced
this issue
Sep 18, 2016
timholy
added a commit
that referenced
this issue
Sep 18, 2016
timholy
added a commit
that referenced
this issue
Sep 18, 2016
timholy
added a commit
that referenced
this issue
Sep 19, 2016
Split getindex and view apart. Closes #38.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I started development of this package, it was somewhat of a testbed for new indexing behaviors. I tried to make the package rather opinionated on how I believed indexing should work. One of those opinions was that indexing should return views by default.
Base Julia has caught up (and surpassed) AxisArrays in terms of APL indexing, but it hasn't caught the view train yet. Should AxisArrays take a step back and match behaviors?
The text was updated successfully, but these errors were encountered: