-
Notifications
You must be signed in to change notification settings - Fork 55
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
Rename based_on()? #52
Comments
I dislike the name |
It looks like that use of (Another possibility would be |
+1 for changing the name. |
Is there still support for this change? Seems like it would be easy to implement if folks still want to do it. |
Yes, I think we should merge |
Thanks for the update; I didn't realize just how current this issue is over on the DataFrames front. I'll revisit the issue a bit later, and if it seems some effort would be appreciated to make this happen on DataFramesMeta, I'll give it a try. |
@pdeffebach Is there any reason to keep EDIT: my bad, |
yes, we will definitely rename |
Closed via #167 |
As noted in #48,
based_on
might not be the best name for this operation. It's hard to distinguish fromgroupby
(and doesn't follow the same naming convention with regard to the underscore).summarize
/summarise
(like dplyr) might be more explicit. But it's a bit surprising that this operation also allows returning as many rows as in the original data, which is completely different from summarizing.I wonder whether it couldn't be merged with
select
, as in SQL. AFAICTselect
doesn't work onGroupedDataFrame
currently, so there would be no conflict.The text was updated successfully, but these errors were encountered: