GitHub user jodersky opened a pull request:
https://github.com/apache/spark/pull/9925
[SPARK-7286] [SQL] Deprecate !== in favour of =!=
Fixes subtle issues related to operator precedence, as discussed in
SPARK-7286.
I'm not entirely sure this is the right thing to do, personally I think
operator overloading is a slippery slope to symbol soup. Please feel free to
comment on alternatives.
I anticipated this for Spark 1.7, let me know if I should change the
deprecation warnings.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jodersky/spark operator-precedence
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/9925.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #9925
----
commit 87469238b743b788ac1fdf2d1b7dfee5cb711c2a
Author: Jakob Odersky <joder...@gmail.com>
Date: 2015-11-24T01:01:06Z
Deprecate !== in favour of =!=
Fixes subtle issues related to operator precedence, as discused in
SPARK-7286.
----
---
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
