Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/20#issuecomment-38285370
@ScrapCodes by the way - I don't think this forfeits all of the
functionality. If someone goes and makes a class `private` that was not
previously `private` it's an obvious change in visibility and something we can
easily see during reviews. The much bigger issue are when people change
functions and traits in a way that actual breaks compatibility but is hard to
detect/notice (for instance, if you change a `val` to a `def` in a trait, it is
invalid). Those cases are the hardest ones and they will still be caught here.
---
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.
---
