Populate an isolated environment (typically created with `new.env(parent = baseenv())`) with objects needed to mimic the standard Base R package surface during coverage or test evaluation.
load_base_r_packages_into_env(env, overwrite = FALSE)A named list with two character vectors:
Exported objects copied from Base R packages other than `base` and `datasets`.
Dataset objects loaded from the `datasets` package.
An environment to populate.
Logical; if `TRUE`, overwrite objects already present in `env`. If `FALSE` (default), existing objects are left unchanged.
The `base` package itself is already available via `baseenv()` and is therefore not copied into `env`. The function instead:
- loads datasets from the `datasets` package into `env`, and - copies exported objects from other Base R packages into `env` (e.g. `stats`, `utils`, `graphics`, `grDevices`, `methods`, etc.).
This is useful when tests are evaluated in a deliberately isolated environment whose parent is `baseenv()`, because objects from packages such as `stats` (e.g. `rnorm`) and `datasets` (e.g. `mtcars`, `iris`) are not automatically visible there.
The Base R package set handled here is:
`base`
`compiler`
`datasets`
`graphics`
`grDevices`
`grid`
`methods`
`parallel`
`splines`
`stats`
`stats4`
`tcltk`
`tools`
`utils`
Because `base` is already reachable through `baseenv()`, it is excluded from the explicit copy step.