Skip to content

/ arrayfire-python

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

Jump to bottom

array[0:0] should return empty array #26

Closed
FilipeMaia opened this issue Aug 28, 2015 · 4 comments
Closed

array[0:0] should return empty array #26

FilipeMaia opened this issue Aug 28, 2015 · 4 comments
Labels
bug
Milestone
3.4

Comments

@FilipeMaia
Copy link
Contributor

@FilipeMaia FilipeMaia commented Aug 28, 2015

Currently it is equivalent to array[:] which is quite surprising.
@pavanky pavanky mentioned this issue Aug 28, 2015
Closed
@FilipeMaia
Copy link
Contributor Author

@FilipeMaia FilipeMaia commented Aug 28, 2015

As empty arrays don't really exist yet a good compromise might to to return None.
@pavanky
Copy link
Member

@pavanky pavanky commented Aug 28, 2015

They do exist. array(dim4()) is an empty array in ArrayFire. The functions not handling them properly is a different issue..
@pavanky pavanky added the bug label Nov 13, 2015
@pavanky pavanky modified the milestone: 3.3 Dec 19, 2015
@pavanky
Copy link
Member

@pavanky pavanky commented Mar 20, 2016

This is partially solved when using logical indexing in devel.
@pavanky pavanky modified the milestones: 3.3, 3.4 Mar 20, 2016
@pavanky pavanky modified the milestones: 3.4, 3.5 Sep 24, 2016
@pavanky
Copy link
Member

@pavanky pavanky commented Sep 25, 2016

This is fixed in devel.
@pavanky pavanky closed this Sep 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
3.4
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@FilipeMaia @pavanky
You can’t perform that action at this time.