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/921#issuecomment-236271882,https://api.github.com/repos/pydata/xarray/issues/921,236271882,MDEyOklzc3VlQ29tbWVudDIzNjI3MTg4Mg==,5635139,2016-07-29T19:26:50Z,2016-07-29T19:26:50Z,MEMBER,"Thanks for the, as ever, thoughtful response

Should we move `Dataset.dims` to be a tuple, then?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,168243768
https://github.com/pydata/xarray/issues/921#issuecomment-236224041,https://api.github.com/repos/pydata/xarray/issues/921,236224041,MDEyOklzc3VlQ29tbWVudDIzNjIyNDA0MQ==,5635139,2016-07-29T16:15:03Z,2016-07-29T16:15:03Z,MEMBER,"I frequently need to pull out the dimension names, and I've never needed to pull out their sizes. I realize that the internals need to do that though. And maybe my use case is specific.

Zooming out a bit: the access pattern for most of these (variables, coords) is indeed an `OrderedDict` of name to object. But the stickler for dim is why the size should be the value here? It seems very different from having dim objects as values.

I could certainly understand a convenience `dims_shape` (for `{dim: ds[dim].shape for dim in ds.dims}`.

But I""m coming from a place of less context without that much confidence...
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,168243768
https://github.com/pydata/xarray/issues/921#issuecomment-236093456,https://api.github.com/repos/pydata/xarray/issues/921,236093456,MDEyOklzc3VlQ29tbWVudDIzNjA5MzQ1Ng==,5635139,2016-07-29T04:45:32Z,2016-07-29T04:45:32Z,MEMBER,"What are the arguments against having `dims` be a tuple for both `DataArray` & `Dataset`s? 
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,168243768