Athan

@honno Has this been resolved or does more work remain?

> Was there ever an analysis done of what integer array indexing the different array libraries support? No, not in explicit detail.

Based on the history of NEP 21 (https://numpy.org/neps/nep-0021-advanced-indexing.html) and the following related discussions - Discussion: (the first half of the thread is most relevant) - Discussion: - Discussion: - Orthogonal...

@vnmabus That is essentially NEP 21. Not opposed, but also that proposal was written in 2015 and still draft. There the naming conventions were `oindex` and `vindex`. In general, in...

> The response I expect to that from numpy folks at least (and it'd be my own too) is "why a keyword, we already covered this with separate functions". NumPy...

Of the options discussed thus far, my personal preference is following SciPy in having a "nan_policy" kwarg. The "omit" and "propagate" options map cleanly to `nan*` and non-nan versions and...

Updated the PR to include methodology section. Linking to this section from the compat table section is still TBD and a bit tricky to do elegantly given that compat tables...

@rgommers Thanks for taking a look. In terms of feedback, this can be split into two parts: (1) what this PR achieves (i.e., UI/UX) and (2) compat data as compiled...

For reference, a more birds-eye view of compat data can be found at the following link: .

I second @rgommers opinion that we should continue authoring as functions, rather than as classes. Authoring as classes increases authoring complexity and just raises contribution barriers. I'd prefer to hide...