Skip to content

Conversation

@lidavidm
Copy link
Member

Also fixes a major bug in grouped var/std, where multiple batches fed to the same state instance would improperly update state.

@github-actions
Copy link

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like most of this could be factored out to reuse in both GroupByUsingExecPlan overloads.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason we don't want to be explicit in our capture here?

Copy link
Member

@pitrou pitrou Aug 25, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may capture explicitly when lifetime is at stake, e.g. in async code where it's important to delineate what exactly needs to survive past the enclosing scope. Here, the callable is executed synchronously, listing every capture explicitly is more of a nuisance (both for typing and readability-wise).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@felipeblazing Out of curiosity, why do you think capturing explicitly would be better here?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we also capture explicitly here?

Copy link
Member

@pitrou pitrou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 from me. @felipeblazing Feel free to review again as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants