structured `void` dtypes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 79
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The void scalar type should be made generic, with parameters bound to the (optional) nested field dtypes (.fields), and perhaps also its shape (.shape).
The fields type parameter should be bound to Mapping[str, tuple[dtype, int] | tuple[dtype, int, str]] | None, so that a TypedDict can be used to precisely specify the structure.
Note to self: Once implemented, be sure to also update the numpy.lib.recfunctions accordingly.
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.
Research direction
Start by reviewing the existing typing for the void scalar and the numpy.lib.recfunctions stubs. Define how optional nested .fields mappings and possibly .shape should be represented generically, then update the related recfunctions types. Done means void supports the intended precise TypedDict-based structure and the dependent stubs remain consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100