`same_kind` casting type-aliases
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- numpy, python
- Domain
- developer-experience, tooling
Research direction
The issue names no files or tests. Start by locating the existing _numtype aliases that implement the casting='safe' rules, then compare them with the requested same_kind table. Done means equivalent same-kind type-aliases are implemented and their behavior is verified against the table.
Written by the indexing model from the issue text.
Description
Currently, only the safe (NEP 50) casting rules are implemented (as _numtype type-aliases). For the sake of completeness, the same-kind should also have similar type-aliases.
casting = 'safe'
b1 -> b1 u1 u2 u4 u8 i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
u1 -> u1 u2 u4 u8 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
u2 -> u2 u4 u8 i4 i8 m8 f4 f8 c8 c16 S U T V O
u4 -> u4 u8 i8 m8 f8 c16 S U T V O
u8 -> u8 f8 c16 S U T V O
i1 -> i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
i2 -> i2 i4 i8 m8 f4 f8 c8 c16 S U T V O
i4 -> i4 i8 m8 f8 c16 S U T V O
i8 -> i8 m8 f8 c16 S U T V O
m8 -> m8 T V O
f2 -> f2 f4 f8 c8 c16 S U T V O
f4 -> f4 f8 c8 c16 S U T V O
f8 -> f8 c16 S U T V O
c8 -> c8 c16 S U T V O
c16 -> c16 S U T V O
S -> S U V O
U -> U V O
T -> T O
V -> V O
O -> O
M8 -> T V O M8
casting = 'same_kind'
b1 -> b1 u1 u2 u4 u8 i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
u1 -> u1 u2 u4 u8 i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
u2 -> u1 u2 u4 u8 i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
u4 -> u1 u2 u4 u8 i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
u8 -> u1 u2 u4 u8 i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
i1 -> i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
i2 -> i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
i4 -> i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
i8 -> i1 i2 i4 i8 m8 f2 f4 f8 c8 c16 S U T V O
m8 -> m8 T V O
f2 -> f2 f4 f8 c8 c16 S U T V O
f4 -> f2 f4 f8 c8 c16 S U T V O
f8 -> f2 f4 f8 c8 c16 S U T V O
c8 -> c8 c16 S U T V O
c16 -> c8 c16 S U T V O
S -> S U T V O
U -> U T V O
T -> b1 S U T V O
V -> T V O
O -> O
M8 -> T V O M8
- Dominant language
- Python
- Stars
- 79
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
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.
More from numpy/numtype
-
topic: documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
topic: documentation
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
blame: Pyright tool: basedpyright
-
numpy.generic stubs: Incomplete
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
_numtype stubs: Refactor
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
sponsored
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Diaoul/subliminal#1382 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100