add 'should' suggestion for `NotImplemented` and reflected operators

Open
#993 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation, tooling

Research direction

Start with the linked discussion in array-api-strict issue 188 and the referenced HackMD section to understand the agreed wording and scope. Locate the relevant array API specification text and the array-api-strict behavior, then verify that the specification uses “should” for unknown types and strict follows that guidance, including any documented flag decision.

Written by the indexing model from the issue text.

Description

see discussion at https://github.com/data-apis/array-api-strict/issues/188

This issue was discussed at hackmd.io/zn5bvdZTQIeJmb3RW1B-8g#Reflected-operators-and-array-api-strict-Lucas. The resolution seemed to be that we would update the spec to state that array libraries should return NotImplemented for unknown types (not must since NumPy probably won't), and update array-api-strict to obey the should. We could also make strict either implement this or not based on a flag.

Dominant language
Python
Stars
281
Forks
52
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from data-apis/array-api

All issues in data-apis/array-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.