search for: conflict_prefer

...raised back again. Such behaviour is similar in spirit to how 'conflicted' R package works, which prints for example, for dplyr::filter : Error: [conflicted] `filter` found in 2 packages. Either pick the one you want with `::` * dplyr::filter * stats::filter Or declare a preference with `conflict_prefer()` * conflict_prefer("filter", "dplyr") * conflict_prefer("filter", "stats") Where the user will only have to copy "conflict_prefer("filter", "dplyr")" and paste it into his script. The difference, is that with: options(conflict...

...brary(conflicted) library(dplyr) library(MASS) select #> Error: [conflicted] `select` found in 2 packages. #> Either pick the one you want with `::` #> * MASS::select #> * dplyr::select #> Or declare a preference with `conflicted_prefer()` #> * conflict_prefer("select", "MASS") #> * conflict_prefer("select", "dplyr") conflicted works by attaching a new ?conflicted? environment just after the global environment. This environment contains an active binding for any ambiguous bindings. The conflicted environmen...

...ibrary(conflicted) library(dplyr) library(MASS) select #> Error: [conflicted] `select` found in 2 packages. #> Either pick the one you want with `::` #> * MASS::select #> * dplyr::select #> Or declare a preference with `conflicted_prefer()` #> * conflict_prefer("select", "MASS") #> * conflict_prefer("select", "dplyr") I don't know if this is a typo in your r-devel message or a typo in the error message, but you say `conflicted_prefer()` in one place and conflict_prefer() in the other. conflicted works b...

...r is similar in spirit to how 'conflicted' R package > works, which prints for example, for dplyr::filter : > > Error: [conflicted] `filter` found in 2 packages. > Either pick the one you want with `::` > * dplyr::filter > * stats::filter > Or declare a preference with `conflict_prefer()` > * conflict_prefer("filter", "dplyr") > * conflict_prefer("filter", "stats") > > Where the user will only have to copy "conflict_prefer("filter", > "dplyr")" and paste it into his script. The difference, is tha...

...y(MASS) > > select > #> Error: [conflicted] `select` found in 2 packages. > #> Either pick the one you want with `::` > #> * MASS::select > #> * dplyr::select > #> Or declare a preference with `conflicted_prefer()` > #> * conflict_prefer("select", "MASS") > #> * conflict_prefer("select", "dplyr") I don't know if this is a typo in your r-devel message or a typo in the error message, but you say `conflicted_prefer()` in one place and conflict_prefer() in the other. > >...

...library(MASS) > > select > #> Error: [conflicted] `select` found in 2 packages. > #> Either pick the one you want with `::` > #> * MASS::select > #> * dplyr::select > #> Or declare a preference with `conflicted_prefer()` > #> * conflict_prefer("select", "MASS") > #> * conflict_prefer("select", "dplyr") > > conflicted works by attaching a new ?conflicted? environment just after > the global environment. This environment contains an active binding for > any ambiguous bindings. T...

...error you're looking to protect them from, and with even less ability to understand why because they are already doing "The right thing" to protect themselves by using conflicted in the first place... > Finally, as mentioned above, the user can declare preferences: > > conflict_prefer("select", "MASS") > #> [conflicted] Will prefer MASS::select over any other package > conflict_scout(c("dplyr", "MASS")) > #> 1 conflict: > #> * `select`: [MASS] > > I deeply worry about people putting this kind of t...