A few times I'd wish there was a way to support:
pkg::fun()
while _not_ "exposing" fun() on the search() path when attaching pkg.
Although it would be part of the public / exported API, the only way
to call the function would be via pkg::fun(). This would cover Sean's
use case. It would also
Bioconductors --
The core team has two open positions
https://support.bioconductor.org/p/91548/
Please let your colleagues and connections know, so that we continue to
provide an exceptional resource to the bioinformatics community.
Martin Morgan
This email message may contain legally pr
On 01/24/2017 10:19 AM, Sean Davis wrote:
Hi, all.
I am curious about what folks think about naming conventions for commonly
named functions, some of which are so common that even establishing a
generic would be difficult because of different use cases. Examples
include things like “filter”. O
to me, double colon is preferable to prefix. i am not very clear on the
downside.
"filter" is a good example, so is "metadata", which has a very peculiar
definition
in rmarkdown.
On Tue, Jan 24, 2017 at 10:19 AM, Sean Davis wrote:
> Hi, all.
>
> I am curious about what folks think about naming
Hi, all.
I am curious about what folks think about naming conventions for commonly
named functions, some of which are so common that even establishing a
generic would be difficult because of different use cases. Examples
include things like “filter”. One possibility is to use the Google Sheets
a
