Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7598#issuecomment-123861245
I think there are generally no un-resolvable Scala warnings in Spark, and I
do find it's been necessary several times to go back and squash lots of
warning-generating code that's been committed. Some Scala warnings in 2.10 are
errors in 2.11, even. So, yeah I'd prefer to enforce this more strictly too.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
