Matthieu Gomez

One alternative is that filter/transform/combine could always skip missing (i.e. kwarg `skipmissing = true` is the default).

With `select`, `skipmissing` would apply the functions on row for which none of the argument is missing, return the output on these rows, and missing otherwise (to maintain the same...

Could we think about making `filter`/`transform`/`combine`/`select` have the kwarg `skipmissing = true` by default? It's not unheard of — that's what Stata and Panda (for `combine`) do. Also, `data.table` and...

@nalimilan Yes starting with a kwarg and see how it goes is the right way. The only reason I was mentioning the default value is that 1.0 may mean that...

That would be awesome, thanks! Jus to make sure I understand, what do you mean by `transform/select will throw an error in cases when there is no match and a...

> > transform/select will throw an error in cases when there is no match and a vector is returned > > I mean tat this would still error: > >...

> > Just to clarify, I think the following should work: > > select(df, :a => collect, skipmissing = true) > > Thank you for commenting on this, as (sorry...

That’s interesting. I was leaning on the opposite solution: skipmissing = true default for filter and combine, passmissing = false default for transform. Skipmissing = true for filter is consistent...

@pdeffebach I was using for the behavior I was describing for select/transform, whether it is actually called passmissing or skipmissing.

That’s right, I did not think about that. Note that, the way I understand it, `first` in select, with passmissing = true, would suffer for the same problem (ie it...