prefer functions en masse (#51).
Improvements to conflict detection and resolution:
Reports conflicts involving lazy loaded datasets (#54).
Don't report conflicts involving a
Better handling of conflicts cleared by superset principle: if there is a conflict all functions (including any base functions) are reported, and if there isn't a conflict, no packages are reported (instead of 1) (#47).
Don't report conflict between a function and a non-function (#30).
Conflicts involving a primitive function no longer error (@nerskin, #46, #48).
has_moved() function no longer fails when it encounters a
.Deprecated() with no arguments (#29).
.conflicts environment is correctly removed and replaced each time
a new package is loaded (#28).
conflict_scout() reports all conflicts found with a set of packages.
conflict_prefer() allows you to declare a persistent preference
(within a session) for one function over another (#4).
conflicts now generally expects packages that override functions in base
packages to obey the "superset principle", i.e. that
return the same value of
base::bar(...) whenever the input is not an
error. In other words, if you override a base function you can only extend
the API, not change or reduce it.
There are two exceptions. If the arguments of the two functions are not
compatible (i.e. the function in the package doesn't include all
arguments of the base package), conflicts can tell it doesn't follow
the superset principle. Additionally,
dplyr::lag() fails to follow
the superset principle, and is marked as a special case (#2).
Functions that have moved between packages (i.e. functions with a call to
.Deprecated("pkg::foo")) as the first element of the function body) will
never generate conflicts.
conflicted now listens for
detach() events and removes conflicts that
are removed by detaching a package (#5)
Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.