-
Notifications
You must be signed in to change notification settings - Fork 993
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
unique and duplicated's default value for 'by=' #1284
Comments
I agree. (I'm guessing a "question" issue is soliciting opinions..? I've no opinion on the |
Meant it to be |
I agree--I rarely use the default value for |
that would also refer to |
Help documentation for these functions seems not to have changed. It still says that I discovered this reading through the NEWS for all changes in 1.9.8. |
I am not particularly happy with the current option of
unique/duplicated
havingby = key(x)
as the default, especially because there's no message or warning as to which columns are being used to compute unique values on.Now that
on=
argument is also in place, and we are entertaining the idea of having to set keys less, maybe it's right time to lift this default value so that it's similar to base R? i.e., withcols = seq_along(x)
- see #1283.The text was updated successfully, but these errors were encountered: