Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider slide_by(), .slide_by = / similar + mutate, summarize, reframe #295

Open
brookslogan opened this issue Apr 6, 2023 · 1 comment
Labels
op-semantics Operational semantics; many potentially breaking changes here P3 very low priority

Comments

@brookslogan
Copy link
Contributor

An idea from {transmute,mutate}_scattered_ts was to have something like a slide_by() function followed by a normal {transmute,mutate}. We could apply that same idea to epi_slide and maybe epix_slide, allowing for {mutate,summarize,reframe,group_modify} in the {epi_df,epi_archive} methods for these, plus mirror dplyr 1.1 and have a .slide_by= parameter in each of these. At least sometimes we want a epi_slide_mutate and others an epi_slide_summarize, and this might be one way to organize this. But this interacts with other interface&naming issues that have not been settled. (E.g., should we have version_slide_by, time_slide_by, version_time_slide_by? Is there actually a mutate parallel for epix_slide? ...)

@brookslogan brookslogan added P3 very low priority op-semantics Operational semantics; many potentially breaking changes here labels Apr 6, 2023
@brookslogan
Copy link
Contributor Author

This could get even more complicated considering the non-reordering of .by.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
op-semantics Operational semantics; many potentially breaking changes here P3 very low priority
Projects
None yet
Development

No branches or pull requests

1 participant