Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Should broadcast_arrays return a tuple instead of a list?

Open
#934 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start with the broadcast_arrays entry in the array API specification and compare the NumPy, Dask, CuPy, and ndonnx behavior linked in the issue. Determine whether the standard should require a tuple instead of a list, then update the specification and affected conformance expectations so implementations agree.

Written by the indexing model from the issue text.

Description

Currently, broadcast_arrays is mandated to return a list. A tuple appears more appropriate on face value, though. NumPy and Dask are, in fact, returning tuples from this function. However, cupy follows the letter of the standard and returns a list. ndonnx is currently returning a list, too, but we would be willing to migrate over to returning a tuple.

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.