Function names

[pkq]

This package is a great idea, especially for those of us with strong tidyverse tendencies who are cognizant of heavy ‘Imports’ dependencies, but not necessarily well-equipped to replicate that functionality ourselves. A couple musings about function names...

1. Incorporating tidyverse package name: As the number of functions and tidyverse packages supported (presumably) grows, I wonder if it would be useful to incorporate the package name in the function name. Something like, use_purrr_detects, use_purrr_walkers, use_tidyr_tidiers. Doing so would group functions from the same package together, and provide pointers in cases where one knows they need base versions of purrr functions, but not exactly how the family of functions is labeled in freebase.

2. Mapping to tidyverse function names: Most of the generated functions map 1:1 to their tidyverse sibling, but there are a few exceptions. I think it would be good to be consistent about that. Are there downsides/issues with the 1:1 mapping? If not, making them all that way seems like the best approach. If there are issues I'm not thinking of, would it make sense to adopt a common prefix (perhaps something like freebase_ or base_ or fb_)?