issue_comments: 364616100
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/1899#issuecomment-364616100 | https://api.github.com/repos/pydata/xarray/issues/1899 | 364616100 | MDEyOklzc3VlQ29tbWVudDM2NDYxNjEwMA== | 6815844 | 2018-02-10T01:47:54Z | 2018-02-10T01:47:54Z | MEMBER | I am inclined to the option 1, as there are some benefit even for backend without the vectorized-indexing support,
e.g.
in case we want to get three diagonal elements (1, 1), (2, 2), (3, 3) from a 1000x1000 array. What we want is
A drawback is that it is difficult for users to predict how large memory is necessary. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
295838143 |