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/702#issuecomment-171503989,https://api.github.com/repos/pydata/xarray/issues/702,171503989,MDEyOklzc3VlQ29tbWVudDE3MTUwMzk4OQ==,953992,2016-01-14T02:13:04Z,2016-01-14T02:13:04Z,MEMBER,"makes sense about dask.array.dropna

though I think you should dropna if at all possible (or have an option at least)

it IS a bit suprising to get back the full index
not sure how common that will be in practice 
esp if u r stacking multiple levels

finally - think about only supporting sequential stacking as it conceptually makes more sense 
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,124700322
https://github.com/pydata/xarray/pull/702#issuecomment-171422543,https://api.github.com/repos/pydata/xarray/issues/702,171422543,MDEyOklzc3VlQ29tbWVudDE3MTQyMjU0Mw==,953992,2016-01-13T20:26:03Z,2016-01-13T20:26:14Z,MEMBER,"hmm, is `dask.array` dropna not implemented? I don't see why it couldn't conceptually be done (though a bit unfamiliar with the impl)
- `set_index` takes 'data' and makes it an 'index', so that is orthogonal. It would _make_ a new Coordinate. `reset_index` would do the converse.
- `stack/unstack` effectively take existing `Coordinates` and transform between them.

ok makes sense.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,124700322
https://github.com/pydata/xarray/pull/702#issuecomment-171298177,https://api.github.com/repos/pydata/xarray/issues/702,171298177,MDEyOklzc3VlQ29tbWVudDE3MTI5ODE3Nw==,953992,2016-01-13T13:58:57Z,2016-01-13T13:58:57Z,MEMBER,"couple of comments:
- I think the repr, though technically accurate, is a bit misleading. lists of tuples is really only useful as a MI, so why not actually indicate that
- `stack/unstack` (as in [9]) is not idempotent, as you are reconstituting the full cartesian product of levels. This seems a bit odd though (pandas can do this because its is separately tracking what is actually in the index, via the labels), I don't think you have this though?
- these ops are really analogs of `set_index/reset_index`, rather than `stack/unstack`, so might be a bit confusing (though I think I get why you are doing it this way), it makes more sense esp for multi-dim. Maybe explain this in the pandas guide?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,124700322