Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17807
I'm not sure there is one rule for this - we would need to look at it on a
case-by-case basis. Generally we should try to avoid conflict, because it is
inconvenient and breaks any existing code users might have.
The "masked" message unfortunately isn't that accurate either - in reality,
we only masked 3 methods (and we have to document them and so on) and not the
23 listed there. For many, there isn't any hack - just the mere act of adding a
generic is triggering inclusion in this message, and in which case nothing is
"wrong" - say, `predict` for example. That's why we have tests
[here](https://github.com/apache/spark/blob/master/R/pkg/inst/tests/testthat/test_context.R#L24)
and
[here](https://github.com/apache/spark/blob/master/R/pkg/inst/tests/testthat/test_mllib_regression.R#L101)
to make sure it is not broken.
---
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
