pdeffebach

> @pdeffebach - given the discussion we have what use cases of #2211 do you see? I agree with you both. i don't think this is that important. I *do*...

Let's close it if it's easiest. I think DataFramesMeta can handle a lot of it's points.

Yes that is one problem. I've had that before and been frustrated by it. We really need a lazy version of this in Base to be honest... Another issue is...

But ultimately I agree that this kind of ifelse pattern could be handled by a macro or some sort of struct with lazy broadcasting. It's a tool that has general...

> * Have DataFramesMeta simplify the handling of missing values. This could be via a dedicated e.g. `@linqskipmissing` macro or a statement like `skipmissing` within a `@linq` block that would...

My [proposal](https://github.com/JuliaData/DataFrames.jl/issues/2314#issuecomment-656220732) above about "spreading" missing values seems relevant here. ``` select(df, :a => collect, skipmissing = true) ``` This takes `:a`, applies `skipmissing`, collects the result, then loops through...

Sorry what is `passmissing`? the concept of `passmissing` only makes sense to me in `ByRow` where you could conceivably have `missing` as an input instead of a vector.

> Skipmissing = true for combine is consistent with Stata, panda. It is also very easy to do comprehend. I'm not sure that's true. The problem Milan is describing is...

The thing is, people don't really complain about `na.rm = TRUE` though, right? I feel like most of the problems we see about `missing` are really easily fixed by pointing...

That's fair. It would be hard to tackle each of these individually, 1. `filter` should apply `coalesce` by default. 1. `skipmissing = true` should apply `passmissing` to `ByRow` functions 1....