RFC: zero-dimensional `indices` array for `take`
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- python
- Domain
- api, documentation
Research direction
Start with the linked Array API specification for take, then compare its one-dimensional indices requirement with the stated behavior of NumPy, PyTorch, JAX, and CuPy. The issue is an RFC, so done means reaching a decision on zero-dimensional arrays and int indices and updating the standard accordingly.
Written by the indexing model from the issue text.
Description
The standard specifies that the indices array of take must be one-dimensional.
NumPy, PyTorch, JAX, and CuPy all support zero-dimensional indices arrays, too. Of course, all libraries support zero-dimensional (and int) indices for __getitem__.
Should the standard allow zero-dimensional arrays for indices? How about ints?
- Dominant language
- Python
- Stars
- 281
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from data-apis/array-api
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Maintenance
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
All issues in data-apis/array-api
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100