Open mcrumiller opened 1 year ago
This looks good to me but I do have a concern. Currently pl.element
is defined as
Alias for an element being evaluated in an eval expression.
We will need to change this, and create some sort of 'list expression' concept, where list.eval
and list.filter
accept 'list expressions'.
Would love this syntactic sugar. I derived the pl.col(list_col_name).list.eval(pl.element().filter(~ pl.element().is_in([0, 1])))
from first principles, but would way rather have just used the applicable .list.filter(...)
, if it existed.
I've once again been brought here. The double use of pl.element()
is a little cringe.
Yes, would be good
still waiting for it
Problem description
filter
would be a useful addition to thelist
namespace, which could just be syntactic sugar forlist.eval(pl.element().filter(pl.element()...))