You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And possibly vec_if_else() because it would be nice for, say, ggplot2 to be able to use this.
Consider if we can figure out some kind of 1:1 interface that doesn't always require a list for values and haystacks to nicely replace plyr::mapvalues()tidyverse/dplyr#7027 (the list approach is very powerful and general because it allows for 1:m and m:1 replacements, but is not always needed)
The text was updated successfully, but these errors were encountered:
Is it still planned? I saw this was the proposed solution to replacing splicing for dplyr::recode(). Using recode() is slowing down code because of lifecycle, so I wondered if I could rely on a faster vctrs implementation sometimes in the future..
Unfortunately it is taking us longer than expected to get some time for a vctrs release, but this is definitely still something I want to add, as I think a lot of people would like a low level type stable vec_if_else() that doesn't need dplyr (particularly ggplot2)
And possibly
vec_if_else()
because it would be nice for, say, ggplot2 to be able to use this.Consider if we can figure out some kind of 1:1 interface that doesn't always require a list for
values
andhaystacks
to nicely replaceplyr::mapvalues()
tidyverse/dplyr#7027 (the list approach is very powerful and general because it allows for 1:m and m:1 replacements, but is not always needed)The text was updated successfully, but these errors were encountered: