Is it expected that just calling `conflict_prefer()` one time turns on conflict resolution everywhere? about conflicted

[kcarnold]

For a bit more context: some users of tidymodels::tidymodels_prefer() may not actually know about conflicted (what problem it solves, how it works, etc.), they're just following example code from tidymodels' documentation. The error message doesn't give any clue that tidymodels_prefer was the original cause.

(Can conflicted be configured to only care about conflicts that were explicitly preferred?)

[hadley]

In answer to the question in the title: yes.

[sanjmeh]

I faced the same problem so I switched to namespace prefix conflicted:: instead of attaching the package with library(conflicted) but this has landed me in a major performance problem, as raised as a separate issue here #75 (comment)