issue_comments: 589707231
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/3786#issuecomment-589707231 | https://api.github.com/repos/pydata/xarray/issues/3786 | 589707231 | MDEyOklzc3VlQ29tbWVudDU4OTcwNzIzMQ== | 327925 | 2020-02-21T15:40:04Z | 2020-02-21T15:40:04Z | MEMBER | Thanks, it makes sense that dimension order conceptually doesn't matter so much once they're labelled. Though I'd say that as Xarray has public APIs for accessing dimensions by position, changing how something like I'm providing an API for other people to access data as a DataArray, and I'd like to have the dimensions in the order that makes it C contiguous, as a hint about what kinds of operations will be efficient. I know some users also go 'what is this complicated thing?' and extract the numpy array from it, in which case the order is more important. So another option that would work for me would be a separate method that rearranges the dimensions to the order that makes the array C contiguous. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
568968607 |