Orson Peters

Our (newly enforced) policy is that nulls should whenever possible be treated as completely absent by default. The problem with correlation is that you can have a scenario where only...

We would appreciate a PR for this, but currently no core developer effort would go to this right now. In principle almost every operation would enjoy being available on the...

This would also (trivially) resolve https://github.com/pola-rs/polars/issues/12014.

@JulianCologne > Possibly merge `rolling` and `rolling_interval`? No. It's very much intended to separate these two functions as they take different parameters, behave differently, have different implementations, etc. > Add...

> So if the current window has nonNullCount >= min_samples than the complete window values including possible null values is passed to the aggregation function, correct? Correct.

@JulianCologne Enforcing that the current row is in the window is unnecessarily limiting. Being able to aggregate over historical or future records I think is valuable. @MarcoGorelli Yes that is...

> @orlp Could you please give a concreate example / use case. I am honestly really curious to know. @JulianCologne Here are some examples: - For each house on the...

@JulianCologne There is a subtle but large ergonomics issue with `start`/`end`: there is no sensible default value for `closed`. If used on a `date` column, `closed="both"` would result `start="-1w", end=0`...

@JulianCologne Perhaps the default should be `closed="left"` also for `position="center"`. That way for discrete data the length is always respected by default. The user can always choose `closed="center"` if they...

@JulianCologne The only problem in the original proposal is the default choice of `closed="both"` for center. As I already mentioned for `rolling`, a centered window with discrete values will be...