Sebastian Berg

The reason is the later bullet point: > Except in the case of providing a single ellipsis (e.g., A[2:10, ...] or A[1:, ..., 2:5]), the number of provided single-axis indexing...

OK, I am not sure I understand the point. I would agree that there is nothing special at all about 0-D. I.e. to me the whole bullet point only serves...

OK, then the question is if one should abandon disallowing partial indices, for the sake of saving you the `idx = *idx, ...` code line in this case. I do...

FWIW, I like seeing the `, ...` or `, :`. I feel it is helpful verbosity for minimal typing in most places (but `...` is strangely little used with `:`...

It is a slight issue, since `+=` can't work on a read-only arrays, but I agree it's niche enough to not worry about it really. Not sure I like the...

> more for NumPy than for the array API standard though I'll have to disagree until I see a clearer plan on how NumPy could introduce CoW (for read-only arrays?)...

Never realized that memmap were still unsafe here. There may be some subtly here that makes this tricky, but the core of the fix would be to replace: ``` self...

Hmmmm pretty sure that goes through memorview? So if it still crashes, is it a Python bug possibly? Because the mmap knows its exported, I think. Or this is really...

Branching off from the other issue. In principle, if clip was a ufunc, doing such an implementation would be a bit tedious. But from the not ridiculously purist side of...

You are using a development version of GCC 16, and that runs into a highway issue that has been addressed there. We should plan on back-porting a highway update to...