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
pairwise() does not work with most {dplyr} backends:
{dplyr}
fun(col_x, col_y)
@carlomedina you mentioned tidyverse/dbplyr@84ecd65#diff-dc5c5a9f543b08c775b46de4b0befea1cd1339144c4aac39e1fac2ca043af3ceR156 however I'm wondering if this is a more general issue.
When checking the traceback() it seems to have to do with the way the masking is being done:
I did notice that the most recent version of dplyr across() changes a few things in the set-up: https://github.com/tidyverse/dplyr/blob/master/R/across.R (e.g. I'm wondering if tidyverse/dplyr@04309fe#diff-a1a1a8d205afe860a05f3209274131f0db5e8cbd85326bc264b9ac6c8cedc5cd may have made a difference).
So don't know if updating to that or some other subtle change may fix (e.g. #1 ) or may be worth asking someone...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
pairwise() does not work with most
{dplyr}
backends:fun(col_x, col_y)
run in parallel #5 )@carlomedina you mentioned tidyverse/dbplyr@84ecd65#diff-dc5c5a9f543b08c775b46de4b0befea1cd1339144c4aac39e1fac2ca043af3ceR156 however I'm wondering if this is a more general issue.
When checking the traceback() it seems to have to do with the way the masking is being done:
I did notice that the most recent version of dplyr across() changes a few things in the set-up: https://github.com/tidyverse/dplyr/blob/master/R/across.R (e.g. I'm wondering if tidyverse/dplyr@04309fe#diff-a1a1a8d205afe860a05f3209274131f0db5e8cbd85326bc264b9ac6c8cedc5cd may have made a difference).
So don't know if updating to that or some other subtle change may fix (e.g. #1 ) or may be worth asking someone...
The text was updated successfully, but these errors were encountered: