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/7463#issuecomment-1426303358,https://api.github.com/repos/pydata/xarray/issues/7463,1426303358,IC_kwDOAMm_X85VA6l-,43316012,2023-02-10T20:27:10Z,2023-02-10T20:27:10Z,COLLABORATOR,"> I didn't see #1463 ([#1463 (comment)](https://github.com/pydata/xarray/issues/1463#issuecomment-340454702)), though. It feels weird to me that we can mutate an IndexVariable via its `data` property, considering that the underlying index is immutable. IIUC `xarr2.x.data[0] = 45` replaces the full index with a new one? I'm not sure if it is a good idea to allow this. For a pandas index that's probably OK (it is reasonably cheap to rebuild a new index) but for a custom index that is expensive to build (e.g., kd-tree) I don't think this behavior is desirable.

should we then raise an error if someone tries to replace values in an index?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1550792876
https://github.com/pydata/xarray/issues/7463#issuecomment-1426267182,https://api.github.com/repos/pydata/xarray/issues/7463,1426267182,IC_kwDOAMm_X85VAxwu,43316012,2023-02-10T19:53:22Z,2023-02-10T19:53:22Z,COLLABORATOR,"It seems that in copy IndexVariables are treated special and are explicitly excluded from copying.
@benbovy what was the reasoning behind this choice?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1550792876