<!DOCTYPE html>
<html>
<head>
<title></title>
<style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
</head>
<body><div>> Plain indexing arr[...] should return an error for ambiguous cases. [...] This includes every use of vectorized indexing with multiple integer arrays.<br></div>
<div><br></div>
<div>This line concerns me. In scikit-image, we often do:<br></div>
<div><br></div>
<div>rr, cc = coords.T # coords is an (n, 2) array of integer coordinates<br></div>
<div>values = image[rr, cc]<br></div>
<div><br></div>
<div>Are you saying that this use is deprecated? Because we love it at scikit-image. I would be very very very sad to lose this syntax.<br></div>
<div><br></div>
<div>> The current plain indexing allows for the use of non-tuples for multi-dimensional indexing.<br></div>
<div><br></div>
<div>I believe this paragraph is itself deprecated? Didn't non-non-tuple indexing just get deprecated with 1.15?<br></div>
<div><br></div>
<div><br></div>
<div>Other general comments:<br></div>
<div>- oindex in general seems very intuitive and I'm :+1:<br></div>
<div>- I would much prefer some extremely compact notation such as arr.ox[] and arr.vx.<br></div>
<div>- Depending on the above concern I am either -1 or (-1/0) on the deprecation. Deprecating (all) old vindex behaviour doesn't seem to bring many benefits while potentially causing a lot of pain to downstream libraries.<br></div>
<div><br></div>
<div>Juan.<br></div>
</body>
</html>