I got this warning too, so I filed an issue to ask
https://github.com/r-lib/roxygen2/issues/1654
On Mon, Sep 2, 2024 at 2:58 PM John Fox wrote:
>
> As it turned out, I was able to avoid redefining coef.merMod(), etc., by
> making a simple modification to the cv package.
>
> I'm still curious abou
I have been reluctant to pipe up on this because I am no expert on the dark
corners of the S3 dispatch mechanism, but I think unregistered S3 methods in
packages are verboten. Perhaps [1] will shed some light?
[1] https://blog.r-project.org/2019/08/19/s3-method-lookup/
On September 4, 2024 11:2
Thanks Toby and Jeff for chiming in on this.
Jeff: I already read Kurt Hornik's post on "S3 Method Lookup" and quite
a few other sources.
The main point is that failing to register the methods works in that the
methods are nevertheless invoked internally by functions in the package
but don't
Dear John,
the question is not really easy to answer, but there is a nice summary
Kurt pointed me to: The code of checkS3methods() includes the following
comments with the last paragraph containing the short answer to your
question:
## Check S3 generics and methods consistency.
## U
