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/3390#issuecomment-788532882,https://api.github.com/repos/pydata/xarray/issues/3390,788532882,MDEyOklzc3VlQ29tbWVudDc4ODUzMjg4Mg==,1217238,2021-03-02T02:42:37Z,2021-03-02T02:42:37Z,MEMBER,"> Shall we raise a warning in `where` advising the more-efficient syntax? Or shall we skip the call to `where_method`

I'm not sure that either of these is a good idea.

The problem with raising a warning is that this is well-defined behavior. It may not _always_ be useful, but well defined but useless behavior arises all the time in programs, so it's annoying to raise a warning for a special case.

The problem with skipping `where_method` is that now we end up with a potentially inconsistent dtype, depending on the selection. These sort of special cases can be quite frustrating to program around.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,505493879
https://github.com/pydata/xarray/issues/3390#issuecomment-650899323,https://api.github.com/repos/pydata/xarray/issues/3390,650899323,MDEyOklzc3VlQ29tbWVudDY1MDg5OTMyMw==,1217238,2020-06-29T04:34:49Z,2020-06-29T04:34:49Z,MEMBER,"> What about the case of no missing values, when `other` wouldn't be needed? Could the same `dtype` be returned then? This is my case, since I'm re-purposing `where` to do `sel` for non-dimension coordinates.

Could you give a concrete example of what this would look like?

It seems rather unlikely to me to have an example of `where` with `drop=True` where the condition is *exactly* aligned with the grid, such that there are no missing values.

I guess it could happen if you're trying to index out exactly one element along a dimension?

In the long term, the cleaner solution for this will be some form for support for more flexibly / multi-dimensional indexing.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,505493879
https://github.com/pydata/xarray/issues/3390#issuecomment-649964438,https://api.github.com/repos/pydata/xarray/issues/3390,649964438,MDEyOklzc3VlQ29tbWVudDY0OTk2NDQzOA==,1217238,2020-06-26T04:53:32Z,2020-06-26T04:53:32Z,MEMBER,"The trouble with returning the same `dtype` for `uint16` values is that there's no easy way to have a missing value for `uint16`.

I don't entirely remember why we don't allow `other` in `where` if `drop=True`, but indeed that seems like a clean solution.

I suspect it might have something to do with alignment. But as long as `other` is already aligned with the result of aligning `self` and `other` (e.g., if `other` is a scalar, which is probably typical), then it should be fine allow for the `other` argument.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,505493879