[
https://issues.apache.org/jira/browse/SPARK-27683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838546#comment-16838546
]
Stefan Zeiger commented on SPARK-27683:
---
You could create your own type alias in a conditional source file. This should
not affect binary compatibility. It's a lightweight alternative to
scala-collections-compat but it has to live with the same restrictions. In
particular, you won't be able to put the alias into `scala.collection` because
it has to go into a package object (which already exists in the standard
library).
Or you could continue using `TraversableOnce` for now. How many different Scala
versions do you intend to support? I don't see any reason why we would have to
remove it in 2.14, we can't remove it in 3.0, either, because it is supposed to
keep compatibility with 2.14, so the `TraversableOnce` alias shouldn't go away
before Scala 3.1 at the earliest.
> Remove usage of TraversableOnce
> ---
>
> Key: SPARK-27683
> URL: https://issues.apache.org/jira/browse/SPARK-27683
> Project: Spark
> Issue Type: Sub-task
> Components: ML, Spark Core, SQL, Structured Streaming
>Affects Versions: 3.0.0
>Reporter: Sean Owen
>Assignee: Sean Owen
>Priority: Major
>
> As with {{Traversable}}, {{TraversableOnce}} is going away in Scala 2.13. We
> should use {{IterableOnce}} instead. This one is a bigger change as there are
> more API methods with the existing signature.
--
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
