-
Notifications
You must be signed in to change notification settings - Fork 0
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
Checks fail with duckplyr #18
Comments
Here's a reduced example. With library(tibble)
library(lubridate)
library(dplyr)
s <- tibble::tibble(x = 1)
time <- 1 |> as.duration()
s <- s |> mutate(Time = time)
is(s$Time)
#> [1] "Duration" "Timespan" "numeric" "vector" Created on 2024-11-01 with reprex v2.1.1 With library(tibble)
library(lubridate)
library(dplyr)
s <- tibble::tibble(x = 1)
time <- 1 |> as.duration()
s <- s |> mutate(Time = time)
is(s$Time)
#> [1] "numeric" "vector" Created on 2024-11-01 with reprex v2.1.1 |
@krlmlr closing this out since hopefully that reduced example is what you were looking for (specifically, it looks like when a column is created with a lubridate Duration, the class is handled differently between dplyr and duckplyr) |
Thank you very much for your support, this is very helpful! |
The duckplyr package is aimed to be a drop-in replacement for dplyr, with full behavior compatibility. To assert that, I'm running checks with a rigged version of dplyr. This package fails its checks in this scenario.
Details: https://github.com/krlmlr/dplyr/blob/f-revdep-duckplyr/revdep/problems.md .
Learn more about duckplyr: https://duckplyr.tidyverse.org/ .
From the error message, I can't tell immediately what the cause of the failure is. I'd appreciate your help: can you please help digest a reproducible example that shows how duckplyr is behaving differently from dplyr in your use case?
The modified dplyr version can be installed with any of:
Thanks a lot for your help! Please let me know if you have any questions.
Tracker: tidyverse/duckplyr#297.
The text was updated successfully, but these errors were encountered: