issue_comments: 201529862

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/804#issuecomment-201529862 https://api.github.com/repos/pydata/xarray/issues/804 201529862 MDEyOklzc3VlQ29tbWVudDIwMTUyOTg2Mg== 2783717 2016-03-25T21:49:03Z 2016-03-25T21:49:03Z NONE

I'm fine with the duck typing, and could make that work fairly easily. The mutation is a bit trickier though. I see two good options here for what b = dask.compute(a) would do with a being an xarray object: 1. b is a new object with the computation performed, a still contains a dask array (uncomputed). 2. b is the same object as a, and the internals of a are mutated to contain evaluated data.

I'm slightly partial to option 2, as it seems to mesh more with how xarray currently uses dask. Thoughts?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   143551401