You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/08/06 12:32:04 UTC
[jira] [Commented] (SPARK-9613) Ban use of JavaConversions and
migrate all existing uses to JavaConverters
[ https://issues.apache.org/jira/browse/SPARK-9613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659811#comment-14659811 ]
Sean Owen commented on SPARK-9613:
----------------------------------
+1 and I'd like to work on this for 1.6. There are a lot of accidental translations to Java and back just because a Java collections method was invoked on a Scala collection when there's an entirely suitable Scala method. It's a big cross-cutting change but worth it.
> Ban use of JavaConversions and migrate all existing uses to JavaConverters
> --------------------------------------------------------------------------
>
> Key: SPARK-9613
> URL: https://issues.apache.org/jira/browse/SPARK-9613
> Project: Spark
> Issue Type: Improvement
> Reporter: Josh Rosen
>
> Spark's style checker should ban the use of Scala's JavaConversions, which provides implicit conversions between Java and Scala collections types. Instead, we should be performing these conversions explicitly using JavaConverters (or forgoing the conversions altogether if they're occurring inside of performance-critical code).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org