codetools::checkUsagePackage might be adapted or repurposed to say which functions, and maybe which classes, from which other packages, a package uses. Then we could get a finer-grained dependency tree. If everybody's importing package foo, it'd be nice to know why. Sort of a class- and function-level ReverseDepends tree.
codetools::checkUsagePackage might be adapted or repurposed to say which functions, and maybe which classes, from which other packages, a package uses. Then we could get a finer-grained dependency tree. If everybody's importing package foo, it'd be nice to know why. Sort of a class- and function-level ReverseDepends tree.