issue_comments: 644451622
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/issues/1077#issuecomment-644451622 | https://api.github.com/repos/pydata/xarray/issues/1077 | 644451622 | MDEyOklzc3VlQ29tbWVudDY0NDQ1MTYyMg== | 1217238 | 2020-06-16T00:00:40Z | 2020-06-16T00:00:40Z | MEMBER | I agree with @fujiisoup. I think this "compression-by-gathering" representation makes more sense for sparse arrays than for a MultiIndex, per se. That said, MultiIndex and sparse arrays are basically two sides of the same idea. In the long term, it might make sense to try only support one of the two. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
187069161 |