Supersede case_match()
#7735
Merged
Supersede case_match()
#7735
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hadley
approved these changes
Oct 10, 2025
Member
hadley
left a comment
hadley
left a comment
There was a problem hiding this comment.
LGTM! Do you want to do a lifecycle release soon?
Member
Author
Yes that would be great |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In favor of
recode_values()andreplace_values()Bringing in dev lifecycle to ensure we don't release dplyr with degraded
case_match()performance due tolifecycle::signal_stage().Updated all
case_match()tests to show how to transition torecode_values()andreplace_values(), which was very validating