[
https://issues.apache.org/jira/browse/SPARK-27681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837753#comment-16837753
]
Marcelo Vanzin commented on SPARK-27681:
----------------------------------------
bq. we don't need to do this until we support Scala 2.13
I guess my question is why do we need to do it? Your explanation above
indicates that the {{Seq}} alias in 2.13 will just be a different type. That's
fine since 2.12 and 2.13 builds are not binary compatible anyway.
I'd understand this change if the {{Seq}} alias was being removed altogether
and you'd need an explicit import, but that doesn't seem to be the case.
> 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: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
