[
https://issues.apache.org/jira/browse/SPARK-27681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838693#comment-16838693
]
Marcelo Vanzin commented on SPARK-27681:
----------------------------------------
bq. scala.Seq is just a type def for scala.collection.Seq
In 2.12. If you force all the API in 2.13 to explicitly use
{{scala.collection.Seq}}, all the existing user code that does not explicitly
import that class will now be using a different type, and may run into issues.
Again, what I'm asking is why it is important for a method {{def foo(s:
Seq[Any])}} to be exposed as {{def foo(s: scala.collection.Seq[Any])}} in both
Scala 2.12 and 2.13, instead of using whatever is the default {{Seq}} alias for
the respective Scala version.
I really don't know how to word my question any more clearly.
> 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
