conflicted 1.0.0
New functions
-
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).
Improve conflict resolution
-
conflicts now generally expects packages that override functions in base
packages to obey the "superset principle", i.e. thatfoo::bar(...)
must
return the same value ofbase::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)