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

Mark nest_by() and group_*() as questioning rather than experimental #6639

Closed
DavisVaughan opened this issue Jan 12, 2023 · 2 comments · Fixed by #6657
Closed

Mark nest_by() and group_*() as questioning rather than experimental #6639

DavisVaughan opened this issue Jan 12, 2023 · 2 comments · Fixed by #6657
Milestone

Comments

@DavisVaughan
Copy link
Member

  • Since we will probably have nest(.by =) in tidyr
  • And the group_*() family doesn't fit super well in conjunction with the new dplyr .by ideas
@manhnguyen48
Copy link

Hi, dplyr::nest_by returns a rowwise data frame while tidyr::nest(.by=) doesn't. Those are useful to organise tibbles within tibble and not having to use purrr::map on every mutate calls. If nest_by is being phased out perhaps tidyr::nest() could gain a .rowwise=TRUE argument for backward compatibility?

@hadley
Copy link
Member

hadley commented Jan 25, 2023

@manhnguyen48 we are considering a different way to achieve a rowwise() since mutate() is really the only function that rowwise() affects, suggesting that creating a custom class isn't the right approach here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants