[
https://issues.apache.org/jira/browse/SPARK-27681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837751#comment-16837751
]
Sean Owen commented on SPARK-27681:
-----------------------------------
To my understanding, we don't need to do this until we support Scala 2.13. We
_can_ do it now, as it just makes explicit the type of {{Seq}} that is already
used by using the type {{scala.Seq}}. We don't actually want or need to change
to use {{scala.collection.immutable.Seq}} over {{scala.collection.Seq}} in
theory or practice. But indeed, that change wouldn't be so bad anyway as 2.13
builds aren't expected to be binary compatible with 2.12. I'd only argue for it
as the API already doesn't promise immutable or mutable {{Seq}} and this change
would maintain that, but yeah it's not even strictly required.
> Use scala.collection.Seq explicitly instead of scala.Seq alias
> --------------------------------------------------------------
>
> Key: SPARK-27681
> URL: https://issues.apache.org/jira/browse/SPARK-27681
> Project: Spark
> Issue Type: Sub-task
> Components: ML, MLlib, Spark Core, SQL, Structured Streaming
> Affects Versions: 3.0.0
> Reporter: Sean Owen
> Assignee: Sean Owen
> Priority: Major
>
> {{scala.Seq}} is widely used in the code, and is an alias for
> {{scala.collection.Seq}} in Scala 2.12. It will become an alias for
> {{scala.collection.immutable.Seq}} in Scala 2.13. To avoid API changes, we
> should simply explicit import and use {{scala.collection.Seq}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
