Thanks for your excellent exposition of the problem, Ivan. The set-aside option
would be attractive in the long term and make it easier to fix historical
errors like mine. Presumably there is also a downside to creating a safe space
for badly named functions.
I am tossing up between (i) appeali
В Wed, 25 Sep 2024 05:13:31 +
Murray Efford via R-package-devel пишет:
> When I deprecate the old functions (by exporting a shell function
> that calls .Deprecated and the new function), I get a package check
> note for e.g. esa.plot "* checking S3 generic/method consistency ...
> NOTE Appare
May be a completely red herring, but I've recently had what might be a similar
issue with reference classes, which kept me pulling my hair for a few hours
(when method calls that used to work suddenly stopped doing so, unless called
manually first).
IIRC, the culprit was a method obj$basis() be
В Wed, 25 Sep 2024 16:57:55 -0400
Ben Bolker пишет:
> Next question, is this (in your opinion) worth escalating to
> r-devel ?
I think so, yes. Hopefully there will be a way to temporarily re-enable
the S4 dispatch for primitive operators in methods:::.requirePackage
(that lives in R/RClassUtil