In addition, another Conflict Policy could also be adopted, which I will
call "Lazy Method Attachment into the Search Path", understood as:
* All non-conflicting methods are always attached into the Search path.
* If a conflict occurs, method for a specific class object, is not
attached, unless you are going to use it, and then the user is asked in the
command prompt if you want it attached or not.
For example, if I set:
options(conflict.policy = "ask")
# All works fine.
filter(col1 == "a")
#> Do you want to attach data.frame.filter Method? y/n?
This approach would be great for dynamic programming and R Scripting, and
lay somewhere between R Core / @Luke Tierney's approach and "conflicted"