-
Notifications
You must be signed in to change notification settings - Fork 275
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
Should pluck<-
actually be chuck<-
?
#634
Comments
We considered this and thought the interface would be simpler overall this way because casual users wouldn't need to learn the difference between the two and remember that they have to use |
Just got some feedback from @jennybc about
The latter suggests we should have both Also would be useful to have a cc @hadley |
From @hadley: |
I am not sure that
pluck()
andpluck<-()
are consistent.pluck()
returnsNULL
if the element does not exist, butpluck<-()
throws an error. In that way,pluck<-()
feels more like the counterpart tochuck()
.I am not sure that
pluck<-()
should even exist, sinceassign_in()
is very strict and requires that the plucked-location must exist. I am just arguing that is should be namedchuck<-()
instead.Created on 2019-02-04 by the reprex package (v0.2.1.9000)
The text was updated successfully, but these errors were encountered: