Add select_if() to select based on predicate #1880
Merged
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.
This function would be analogous to
summarise_if()
andmutate_if()
.One way to distinguish responsibilities between
select()
andselect_if()
is that the former operates on metadata such as the column names, while the latter operates on the columns themselves, and thus requires local sources.So the custom functions suggested in #1229 would belong to
select()
because they operate on the column names. And more general predicates based on column types (also metadata) compatible with DB sources could be added toselect()
.Closes #497, closes #1569