Since setting DUCKPLYR_METHODS_OVERWRITE to TRUE, should call methods_overwrite() when the package is loaded, I would expect the opposite to happen, when it is set to FALSE.
Though the methods are reported as overwritten regardless. This tested with duckplyr version 1.2.1.
withr::with_envvar(c(DUCKPLYR_METHODS_OVERWRITE = "FALSE"), {
library(duckplyr)
})
Loading required package: dplyr
Attaching package: ‘dplyr’
The following objects are masked from ‘package:stats’:
The following objects are masked from ‘package:base’:
intersect, setdiff, setequal, union
The duckplyr package is configured to fall back to dplyr when it encounters an incompatibility. Fallback events can be collected and uploaded for analysis to guide future development. By default, data will be collected but no data will be uploaded.
ℹ Automatic fallback uploading is not controlled and therefore disabled, see duckplyr::fallback.
✔ Number of reports ready for upload: 2.
→ Review with duckplyr::fallback_review(), upload with duckplyr::fallback_upload().
ℹ Configure automatic uploading with duckplyr::fallback_config().
✔ Overwriting dplyr methods with duckplyr methods.
ℹ Turn off with duckplyr::methods_restore()
Since setting DUCKPLYR_METHODS_OVERWRITE to TRUE, should call methods_overwrite() when the package is loaded, I would expect the opposite to happen, when it is set to FALSE.
Though the methods are reported as overwritten regardless. This tested with duckplyr version 1.2.1.