On 29/06/2014, 3:07 PM, Michael Lawrence wrote:
> While the change to the symbol lookup is generally useful (e.g., for
> finding S4 methods that become available whenever a package is loaded),
> it seems that we ultimately want a mechanism by which a package
> namespace can formally declare that it
Regarding the following code,
warning(sprintf(ngettext(has.errors,
"scheduled core %s encountered error in user code, all values of
the job will be affected",
"scheduled cores %s encountered errors in user code, all values
of the jobs will be affected"),
paste(has.errors, collapse
While the change to the symbol lookup is generally useful (e.g., for
finding S4 methods that become available whenever a package is loaded), it
seems that we ultimately want a mechanism by which a package namespace can
formally declare that it is re-exporting a symbol from some package. Then,
for e
