当您在 .RProfile 中加载库时，在R启动过程中很早就在附加了 stats 包之前。另一方面，您已经加载了 stats 之后附加 dplyr 。我看到Hadley建议不要在 .RProfile 中加载软件包（因为包装加载顺序不一致），虽然我个人对此没有很大的感觉。 （R的启动过程的细节在启动中描述。）

一个可能的解决方案是简单地添加 library（stats）作为脚本中第一个库调用，然后加载 dplyr 。

另一个（长期）选项可以在全球范围内避免这些问题，将您的工作流程从大量脚本转换为一个或多个软件包。

At work, I have a Windows 7 computer running R 3.1.2.

I have a file called packages.R. In my this file, I have the following code:

library(dplyr)
library(sqlutils)
library(RODBC)

My .Rprofile contains a function called .First.

.First <- function() {
    source("R/packages.R")
}

When I load R, I get the following output:

Loading required package: roxygen2
Loading required package: stringr
Loading required package: DBI

Attaching package: 'dplyr'

The following objects are masked from 'package:base':

    intersect, setdiff, setequal, union

If you look at this carefully, you will see the filter from stats is not masked.

But, if I take my exact same setup, and comment out the library(dplyr) statement in packages.R, save the file, and restart R and then manually . . . . as in type it in by hand . . . .

library(dplyr)

Attaching package: 'dplyr'

The following object is masked from 'package:stats':

    filter

The following objects are masked from 'package:base':

    intersect, setdiff, setequal, union

Now, it masks package::stats.

I don't get it. I need to use the filter command from dplyr a lot for this project and I don't want to type dplyr::filter in order to use it. Could someone please help my weak mind understand why this is behaving this way? I have tried starting R in RStudio and ESS, and I get the exact same behavior in both. I also tried moving dplyr to the end of the packages.R file, with no difference to the results. I just want to mask stats::filter. Thanks.

When you load libraries in .RProfile they get attached very early in the R startup process, before the stats package is attached. The other way, you're attaching dplyr after stats has already been loaded. I've seen Hadley recommend against loading packages in .RProfile for this reason (discrepancies in package loading order), although personally I don't have strong feelings about it. (The details of R's startup process are described in ?Startup.)

One possible solution is to simply add library(stats) as the very first library call in your script, before loading dplyr.

Another (long term) option to avoid these sorts of issues more globally would be to transition your workflows from "a large collection of scripts" to one or more packages.