I was thinking of using length(search())+1 to be safe and simple.
Using grep gives higher priority than length while still solving your
issue.
On Mon, Nov 25, 2019 at 3:06 PM Gabor Grothendieck
wrote:
>
> Goold idea. This seems to work.
>
> library(dplyr, pos = grep("package:stats", search())
Goold idea. This seems to work.
library(dplyr, pos = grep("package:stats", search()) + 1)
On Mon, Nov 25, 2019 at 1:27 PM Greg Snow <538...@gmail.com> wrote:
>
> You could use the `pos` arg to place the newly loaded package(s) on
> the search path after the stats package. That would give prio
You could use the `pos` arg to place the newly loaded package(s) on
the search path after the stats package. That would give priority for
any functions in the stats package over the newly loaded package (but
also give priority for any other packages earlier on the search path).
On Sat, Nov 23, 20
library and require have new args in 3.6 giving additional control
over conflicts. This seems very useful but I was wondering if there
were some, preferabley simple, way to give existing loaded packages
priority without knowing the actual conflicts in advance. For example
library(dplyr, excl
4 matches
Mail list logo