issue_comments: 789146762
This data as json
| 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/pull/4979#issuecomment-789146762 | https://api.github.com/repos/pydata/xarray/issues/4979 | 789146762 | MDEyOklzc3VlQ29tbWVudDc4OTE0Njc2Mg== | 3460034 | 2021-03-02T19:13:38Z | 2021-03-02T19:13:38Z | CONTRIBUTOR | It's great to be able to follow along with the discussion here! I'm definitely interested in seeing where the duck array index support ends up. One use-case motivated question: the flexible indexes refactoring has also been pointed to as the resolution to https://github.com/pydata/xarray/issues/2233, where multidimensional coordinates have the same name as one of their dimensions. I wasn't quite able to tell through the narrative here if that has been addressed along the way yet or not ("A. only 1D coordinates with a name matching their dimension name" for implicit index creation does seem to get close though). So, would it be worth directly addressing https://github.com/pydata/xarray/issues/2233 here, or should that wait? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
819062172 |