Open stevecondylios opened 4 years ago
Being able to gauge the popularity of a package can help when making judgement calls around whether a collision is acceptable.
If search CRAN packages for functions named 'present'
collidr::CRAN_collisions("present", CRANdf = getCRAN())
we see 34 packages contain a function of that name
[1] "Retrieving CRAN data.." [1] "Data last updated 2020-01-03 18:30:27 UTC" $packages character(0) $functions package_names function_names 8016 alakazam present 15031 animint2 present 19078 antaresRead present 28380 augmentedRCBD present 58301 CeRNASeek present 61711 ChemoSpec present 72153 cold present 83176 cvGEE present 90010 deldir present 107064 dplR present 139554 fivethirtyeight present 160015 ggparty present 189272 its.analysis present 216668 MapGAM present 226269 metacoder present 235477 mistr present 255366 NetMix present 278640 partykit present 299321 PredPsych present 310647 pubmed.mineR present 313997 PWFSLSmoke present 325289 RAhrefs present 332937 rcosmo present 358489 Rnets present 374933 rSHAPE present 379530 RStoolbox present 381455 rsvd present 386804 sae2 present 390184 samurais present 433109 statsr present 452105 tigger present 454147 timereg present 463534 TSdist present 468571 UncertainInterval present
We now assess whether such a collision is acceptable. In doing so, having the number of downloads for each of these packages would be useful
Same again for CRAN_collisions("otherwise", CRANdf = getCRAN()) ('otherwise' has ~58 collisions - but how to quickly determine how important these are?)
CRAN_collisions("otherwise", CRANdf = getCRAN())
Being able to gauge the popularity of a package can help when making judgement calls around whether a collision is acceptable.
Example
If search CRAN packages for functions named 'present'
we see 34 packages contain a function of that name
We now assess whether such a collision is acceptable. In doing so, having the number of downloads for each of these packages would be useful