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/7045#issuecomment-1251836989,https://api.github.com/repos/pydata/xarray/issues/7045,1251836989,IC_kwDOAMm_X85KnYQ9,12912489,2022-09-20T04:48:07Z,2022-09-20T06:13:32Z,NONE,"This suggestion looks roughly like what we are discussing in https://github.com/pydata/xarray/discussions/7041#discussioncomment-3662179, i.e., using a custom index that avoids this? So maybe the question here is whether such an `ArrayIndex` should be the default?

Aside from that, with my outside perspective (having used Xarray extremely little, looking at the docs and code occasionally, but developing a similar library that does *not* have indexes):

Indexes (including alignment behavior) feel like a *massive* complication of Xarray, both conceptually (which includes documentation and teaching efforts) as well as code. If all you require is the `ArrayIndex` behavior (i.e., exact coord comparison in operations) then the entire concept of indexes is just ballast, distraction in the documentation, and confusion.
**Example**: *Why can't we use `loc`/`sel` with a non-dimension (non-index) coord? --- without index we would just search the coord with no need to limit this to index-coords, and this is often fast enough?*","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1376109308