are you supposed to use conflicted_prefer() in functions?

[beanumber]

Like this: https://github.com/beanumber/fertile/blob/84e85ea4f648f6faf124d0dd56f13576a70a5f5b/R/shims.R#L17

?? @hadley @jennybc

[hadley]

Definitely not — I'd say ignore conflicted for now (i.e. assume that it's not used), and later on I'll show you a trick for doing this sort of shimming that will trick conflicted.

[beanumber]

Point being, if someone does

library(fertile)
library(tidyverse)

Then fertile won't work right, because readr::read_csv() will have precedent over fertile::read_csv(). So what is the best way to make it so that when fertile loads, it always puts its own shims ahead of the real functions?

[beanumber]

Is this what rlang::env_bind() is for?

[beanumber]

@ambertin can you look into a solution for this? How can we make sure that fertile masks the tidyverse functions even if someone loads fertile before tidyverse?

[beanumber]

Since we're already shimming library() and require(), can we add something like:

library <- function(package, ...) {
  detach("fertile", ...)
  base::library(package, ....)
  base::attach("fertile")
}

??