Add flag to enable lazy array behavior
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reading the linked lazy/eager design topic, then inspect the array operations and __int__ behavior in the repository. Determine how an opt-in flag should affect evaluation and which existing behavior should raise an exception; done means the flag is exposed and its behavior is covered by tests.
Written by the indexing model from the issue text.
Description
A flag to enable lazy array behavior would be useful https://data-apis.org/array-api/draft/design_topics/lazy_eager.html.
We have to be careful here because we don't want to actually build a real "lazy" array package here. It should probably just continue to evaluate everything, but make functions like __int__ raise an exception.
- Dominant language
- Python
- Stars
- 34
- Forks
- 14
- Avg merge
- 3m
- Merged PRs (30d)
- 4
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 data-apis/array-api-strict
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
data-apis/array-api-strict#239 · 3 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
data-apis/array-api-strict#245 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
data-apis/array-api-strict#188 · 5 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
data-apis/array-api-strict#168 · 11 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
data-apis/array-api-strict#128 · 3 comments ·
All issues in data-apis/array-api-strict
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·