Explore options other than `attach()` for `paths`

[nicholas-masel]

Background Information

We use assign() to add paths and functions to the search path. CRAN will fail a package immediately for using assign().

Definition of Done

• Paths are still found.
• Autos are still found, multiple different folders can be sourced, with folders taking priority over others if functions exist in both, and autos always take precedence over packages with the same function name.

[nicholas-masel]

We write paths() to a specific environment and attach this to the search path. We could easily store a blank environment within the package and store paths there instead, removing the need for attach for paths().

[nicholas-masel]

An autos() feature is that you can attach multiple environments to the search path, and the order they are attached takes care of which function to use if there are multiple with the same name.

Could we use {conflicted} here to explicitly pick the functions and add them to search?

Steps:

1. Read envsetup config file for autos.
2. Identify conflicts.
3. Use conflicted to set the preferred functions in the search path.

Step 2 needs some more thought.

[nicholas-masel]

Or we can just do what conflicted did?

https://github.com/r-lib/conflicted/blob/4d759ac62d49ec77cb3d16db41e4c40ffa4cfa1e/R/conflicts.R#L29

[nicholas-masel]

Closed by #82