Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14558
Does having ... in setGeneric forces CRAN checks to require @param there?
I think @mengxr point is that so long as the function definition also has
... we could have one @param at the function definition and therefore we only
have to document that once.
If that is the case I think we are ok, we shouldn't have to @param that
twice and the only question is how many function definitions we need to change
to add ...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
