Francesco Bruzzesi

> Does this sound good? If so, [@FBruzzesi](https://github.com/FBruzzesi) did it interest you to try this out? Yes it definitly does! I will try to tackle it - if you don't...

Update: while this is straightforward for eager backends, for lazy ones `int_range` is fairly more complex than a simple row_index. However I don't really see a point in supporting `int_range`...

Hey @dangotbanned yes sorry for not expanding further. There are various approaches that could work, but in practice `int_range` can allow both start and end values. For lazy backends, the...

The workaround exists, it's enough for `row_index`, but not for `int_range`. The proposal here could be to have a doc page in which we add some functionality which are generally...

@MarcoGorelli > hey @FBruzzesi - do you have a solution for > > The workaround exists, it's enough for row_index, but not for int_range. > ? the following for lazy...

@MarcoGorelli are you working on this? I also started 🙈 Also: > in pandas this is groupby(...).cumcount() wouldn't this be useful for `partition_by`? I understood to first implement `order_by` only,...

> thanks for doing this > > not totally sure about this one, some thoughts: > > * the docs now show `IntoImplementation`, rather than a more explicit union >...

Closing in favor of #2971

Thanks for your feedback @riedgar-ms I understand that the internals might change as long as the public facing API stays as is and your answer addresses the case of `DisaggregatedResult`....

> Are you able to make one of the community meetings? Sure, I should be able to join 🤗 Just to confirm what I could find on discord - the...