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/4060#issuecomment-631785279,https://api.github.com/repos/pydata/xarray/issues/4060,631785279,MDEyOklzc3VlQ29tbWVudDYzMTc4NTI3OQ==,2448579,2020-05-20T23:11:41Z,2020-05-20T23:11:41Z,MEMBER,"good point @mathause. Looks like `apply_gufunc` tries to make blockwise infer meta and then does its own thing when that fails:
https://github.com/dask/dask/blob/3b92efff2e779f59e95e05af9b8f371d56227d02/dask/array/gufunc.py#L417-L440 . I don't understand how this can work in all possible cases.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,618081836
https://github.com/pydata/xarray/pull/4060#issuecomment-631706236,https://api.github.com/repos/pydata/xarray/issues/4060,631706236,MDEyOklzc3VlQ29tbWVudDYzMTcwNjIzNg==,2448579,2020-05-20T20:24:32Z,2020-05-20T20:24:32Z,MEMBER,"> If it does, we don't want to set dask='parallelized' but rather let the function handle dask arrays itself.

I think we still need all the current options for the `dask` kwarg. There can be disastrous consequences so it's good to make users explicitly choose the behaviour they want.

> howto properly handle deprecation (eg. meta)

I don't think we should deprecate meta. Not all user functions can deal with zero shaped inputs, so automatically inferring meta need not always work. We've had to add a similar feature for map_blocks (#3575) so I think `meta` should stay.

> keywords of dask.array.apply_gufunc

Shall we add a new `dask_gufunc_kwargs` and pass that down to `appy_gufunc`?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,618081836