-
Notifications
You must be signed in to change notification settings - Fork 70
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
Replace purrr::when()
with if()
equivalents
#1066
Conversation
This function will be deprecated in the next `{purrr}` release (https://github.com/tidyverse/purrr/blob/55c9a8ab8788d878ce9e8e80b867139e46d15395/R/deprec-when.R#L57), and so we should port it over and prevent user-facing deprecation messages.
This is how benchmark results would change (along with a 95% confidence interval in relative change) if be75da3 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
Thanks. I am not sure we should port it since it requires maintenance. Can't we just use |
purrr::when()
purrr::when()
with if()
equivalents
Done. No longer porting over the function.
IIRC, |
Codecov Report
@@ Coverage Diff @@
## main #1066 +/- ##
=======================================
Coverage 91.06% 91.06%
=======================================
Files 46 46
Lines 2685 2685
=======================================
Hits 2445 2445
Misses 240 240
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
This is how benchmark results would change (along with a 95% confidence interval in relative change) if be75da3 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
Should we release a new version before that? |
Yes, I think that would be a good idea. Maybe at the end of this month? Btw, can I upgrade myself from |
This function will be deprecated in the next (1.0.0)
{purrr}
release (https://github.com/tidyverse/purrr/blob/55c9a8ab8788d878ce9e8e80b867139e46d15395/R/deprec-when.R#L57), and so we should remove its usage to prevent user-facing deprecation messages.