Skip to content

Commit 6c56623

Browse files
eed3si9ndwijnand
andauthored
Update _overviews/core/collections-migration-213.md
Co-Authored-By: Dale Wijnand <344610+dwijnand@users.noreply.github.com>
1 parent 54b38f7 commit 6c56623

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_overviews/core/collections-migration-213.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ In Scala 2.13 `scala.Seq[+A]` is an alias for `scala.collection.immutable.Seq[A]
3636

3737
If you're making an application, and simply migrating a Scala 2.12 code base to 2.13, it might be ok to keep using `scala.Seq` in your code.
3838

39-
If you're making a library intended to be used by other programmers, then using `scala.Seq` or vararg is going to be a breaking change in the API semantics. For example, if there was a function `def orderFood(order: Seq[Order]): Seq[Food]`, previously the library user would have been able to pass in an array of `Order`, but it won't work for 2.13.
39+
If you're making a library intended to be used by other programmers, then using `scala.Seq` or varargs is going to be a breaking change in the API semantics. For example, if there was a function `def orderFood(order: Seq[Order]): Seq[Food]`, previously the library user would have been able to pass in an array of `Order`, but it won't work for 2.13.
4040

4141
- if you cross build with Scala 2.12 and want to maintain the API semantics for 2.13 version of your library, or
4242
- if your library users frequently uses mutable collections such as `Array`

0 commit comments

Comments
 (0)