Enable better indexing 3rd and 4th dimensions.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- fortran
- Domain
- data
Research direction
Start by reading the issue and the linked forum post to understand the intended indexing behavior for array-valued third and fourth dimensions. Trace the wrapper's indexing entry points and existing integer handling; done means arrays work in both dimensions without breaking current integer indexing, with coverage for the new cases.
Written by the indexing model from the issue text.
Description
Right now only integers are allowed for third and fourth dimensions. Add functionality where third and fourth dimensions can be arrays as well.
- Dominant language
- Fortran
- Stars
- 24
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 arrayfire/arrayfire-fortran
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
arrayfire/arrayfire-fortran#3 · 1 assignee ·
All issues in arrayfire/arrayfire-fortran
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
desihub/desisurveyops#486 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
scverse/spatialdata#1256 ·