html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/4240#issuecomment-1258874354,https://api.github.com/repos/pydata/xarray/issues/4240,1258874354,IC_kwDOAMm_X85LCOXy,2086210,2022-09-27T02:14:28Z,2022-09-27T02:14:28Z,NONE,"+1 
Complicated, still vexing this user a year+ later, but it easier for me to just restart the kernel again and again than read this and #4879, which is closed but didn't seem to have succeeded if I read correctly? ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,662505658
https://github.com/pydata/xarray/issues/1613#issuecomment-1062281975,https://api.github.com/repos/pydata/xarray/issues/1613,1062281975,IC_kwDOAMm_X84_USL3,2086210,2022-03-08T22:26:07Z,2022-03-08T22:26:07Z,NONE,"Agreed, new rather than redefine existing meanings. 
Who has the chops and the cred to implement it? Not quite me... ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,263403430
https://github.com/pydata/xarray/issues/1613#issuecomment-1062142845,https://api.github.com/repos/pydata/xarray/issues/1613,1062142845,IC_kwDOAMm_X84_TwN9,2086210,2022-03-08T19:49:33Z,2022-03-08T19:49:33Z,NONE,"How about an informative warning when returning an empty set, as a minimal change? What's the path to an action item here? ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,263403430
https://github.com/pydata/xarray/issues/1613#issuecomment-1058446923,https://api.github.com/repos/pydata/xarray/issues/1613,1058446923,IC_kwDOAMm_X84_Fp5L,2086210,2022-03-03T20:19:56Z,2022-03-03T20:19:56Z,NONE,"@shoyer, `selection over non-monotonic indexes, merely based on matching bounds` is a case I never considered... probably a rare one, which I for one would happily sacrifice. 

New syntax like your first suggestion, `.Between` instead of `.slice` if I understand correctly, could be appealing too:  The word 'slice' has never seemed terribly intuitive to this user, and 'between' is high in an alphabetical list of tips/suggestions a good IDE might bring up with the tab key or whatever. ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,263403430
https://github.com/pydata/xarray/issues/1613#issuecomment-1058341139,https://api.github.com/repos/pydata/xarray/issues/1613,1058341139,IC_kwDOAMm_X84_FQET,2086210,2022-03-03T18:13:31Z,2022-03-03T20:03:15Z,NONE,"How about: add one code line at the top of `slice` that properly orders the exactly two arguments (in other words, reverses the order if necessary)? I haven't studied the code at all, this may be naive. This may the same as 1. above (make `sel` ignore order). Ideally the default would be silently improved, rather than creating something optional that users would have to make a new habit of, like an additional kwarg or new syntax. ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,263403430