The problem is that there's no way to declare that an internal function
should or shouldn't be treated as an S3 method, other than by declaring
it as one in NAMESPACE and exporting it. If you read the thread
"Unfortunate function name generic.something​" that started last week,
you'll see the
Dear R package developers
My emmeans package failed preliminary checks when I submitted an update today,
apparently due to a recent change in requirements on method registration. The
message I got was:
* checking S3 generic/method consistency ... NOTE
Apparent methods for exported generics not
