The obvious solution is to contact the maintainer of the package generating the
spurious warning and have it addressed 'at source'.
Probably it helps to be specific about the package generating the warning, the
nature of the warning, and a link to your package.
I would view assignInNamespace as
This in not well thought through, but what about using `sink` to capture
any messages from the call? Then you might be able to remove the
expected warning and output any remaining warnings if they are there...
However, note this part of `help(sink)`:
Sink-ing the messages stream should be done
Hello,
I'm considering a package submission. I have used assignInNamespace,
which is hideous but seems better than the alternatives. I see that it
returns a NOTE on R CMD check, suggesting that it is not absolutely
prohibited, but would require justification.
The justification I would make is tha
