Github user huitseeker commented on the pull request:
https://github.com/apache/spark/pull/1069#issuecomment-46004365
It resolves the warning the following warning, which occurs in different
(but easy-to-reach) contexts depending on whether you are running with the
`-language` option and your version of Scala :
```sbt
[WARNING] your/source/File.scala:42: warning: postfix operator foo should
be enabled
[WARNING] by making the implicit value scala.language.postfixOps visible.
[WARNING] This can be achieved by adding the import clause 'import
scala.language.postfixOps'
[WARNING] or by setting the compiler option -language:postfixOps.
[WARNING] See the Scala docs for value scala.language.postfixOps for a
discussion
[WARNING] why the feature should be explicitly enabled.
````
(aforementioned
[scaladoc](http://www.scala-lang.org/api/2.11.1/index.html#scala.language$@postfixOps:languageFeature.postfixOps))
Like other features in
[SIP-18](http://docs.scala-lang.org/sips/completed/modularizing-language-features.html),
postfix operators ([spec
6.1.2](http://www.scala-lang.org/docu/files/ScalaReference.pdf#page=92)) are
modularized. [This](http://stackoverflow.com/a/13011301) SO answer gives a hint
at why : in some cases, it adds some parser ambiguity which is not always
obvious to resolve without some experience with the issue.
The choice of whether to add the flag globally or piecewise is mostly a
maintainability issue : if people editing the code base are expected to be able
to handle the potential parser errors fired when editing with this option
turned on, it may make more sense to leave it on globally.
---
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.
---
