We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
chuck()
pluck()
I accidentally used chuck() instead of pluck() and was quite confused by the error as I provided a default. It was something along the lines of
purrr::chuck(list(a = NULL), "a", .default = "a") #> Error: Plucked object can't be NULL
Created on 2020-08-13 by the reprex package (v0.3.0)
Then I realised that I actually wanted to use pluck() and .default was actually used as an index.
.default
I guess chuck() and pluck() should use ellipsis::check_dots_unnamed(). At least for chuck() and .default this would make sense.
ellipsis::check_dots_unnamed()
The text was updated successfully, but these errors were encountered:
Check dots in pluck() and chuck()
814a75b
Fixes #788
Check dots in pluck() and chuck() (#897)
01d19d3
Successfully merging a pull request may close this issue.
I accidentally used
chuck()
instead ofpluck()
and was quite confused by the error as I provided a default. It was something along the lines ofCreated on 2020-08-13 by the reprex package (v0.3.0)
Then I realised that I actually wanted to use
pluck()
and.default
was actually used as an index.I guess
chuck()
andpluck()
should useellipsis::check_dots_unnamed()
. At least forchuck()
and.default
this would make sense.The text was updated successfully, but these errors were encountered: