[jira] [Commented] (SPARK-27682) Avoid use of Scala collection classes that are removed in 2.13
[
https://issues.apache.org/jira/browse/SPARK-27682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838885#comment-16838885
]
Stavros Kontopoulos commented on SPARK-27682:
-
Removing .to[...] means creating explicitly the type you needs a bit verbose I
guess but its the less intrusive option.
> Avoid use of Scala collection classes that are removed in 2.13
> --
>
> Key: SPARK-27682
> URL: https://issues.apache.org/jira/browse/SPARK-27682
> Project: Spark
> Issue Type: Sub-task
> Components: ML, MLlib, Spark Core, SQL
>Affects Versions: 3.0.0
>Reporter: Sean Owen
>Assignee: Sean Owen
>Priority: Minor
>
> Scala 2.13 will remove several collection classes like {{MutableList}}. We
> should avoid using them and replace with similar classes proactively.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-27682) Avoid use of Scala collection classes that are removed in 2.13
[
https://issues.apache.org/jira/browse/SPARK-27682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837906#comment-16837906
]
Sean Owen commented on SPARK-27682:
---
Looks like we can replace usages of removed collections mentioned at
https://docs.scala-lang.org/overviews/core/collections-migration-213.html and
can remove use of .to[...], but remove collection.breakOut will have to wait as
its replacement is only in 2.13 and its use is important for performance, it
seems.
> Avoid use of Scala collection classes that are removed in 2.13
> --
>
> Key: SPARK-27682
> URL: https://issues.apache.org/jira/browse/SPARK-27682
> Project: Spark
> Issue Type: Sub-task
> Components: ML, MLlib, Spark Core, SQL
>Affects Versions: 3.0.0
>Reporter: Sean Owen
>Assignee: Sean Owen
>Priority: Minor
>
> Scala 2.13 will remove several collection classes like {{MutableList}}. We
> should avoid using them and replace with similar classes proactively.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
