summaryrefslogtreecommitdiff
path: root/numpy/array_api/_set_functions.py
diff options
context:
space:
mode:
authorSebastian Berg <sebastian@sipsolutions.net>2022-01-25 12:08:36 -0600
committerSebastian Berg <sebastian@sipsolutions.net>2022-01-29 06:04:34 -0800
commitd70702cca056e1c9c4419ea6d3ec71d7708fe281 (patch)
treec01b7ebeb995ddeb4df833d0b6914fdff89fdf3f /numpy/array_api/_set_functions.py
parent20d5bb76dc0d1324ccc7a9ffa6932ea1bbf1af4d (diff)
downloadnumpy-d70702cca056e1c9c4419ea6d3ec71d7708fe281.tar.gz
API: Allow setting `_get_loop` from experimental API
Get-loop as a mechanism is pretty important to be public, just the signature should probably be modified in the future. So we should make it public, but not hold back on replacing it (and deprecating the current version). To re-iterate the two main changes, I see are: 1. `move_references` is mostly unused and not good API. I believe it is only used for transfer to NULL. But that means it is only used as a DECREF function. A DECREF function is special enough to be special though. 2. I do not like `aligned` as a single flag, I am considering if we should pass a power-of-two alignment, stored in a byte for each "operand". In theory 4-bits of information seem enough for this. (3-bits only reaches `2**(2**3-1) == 128`, so 4 seems better.)
Diffstat (limited to 'numpy/array_api/_set_functions.py')
0 files changed, 0 insertions, 0 deletions