Review Seq matching when porting to 2.13
Briefly

from underscore.io4 years ago
When pattern matching on Seq from a library in Scala 2.13, you must ensure you understand the type of Seq you are handling due to changes in its nature.
underscore.iohttps://underscore.io/blog/posts/2020/05/14/porting-and-seq.html
The migration from Scala 2.12 to 2.13 can cause runtime issues with pattern matching on Seqs, particularly if they come from libraries that don't follow the new default behavior.
underscore.iohttps://underscore.io/blog/posts/2020/05/14/porting-and-seq.html
Scala 2.13 defaults to immutable Seqs. If a library returns a mutable scala.collection.Seq, it may not match your pattern in 2.13.
underscore.iohttps://underscore.io/blog/posts/2020/05/14/porting-and-seq.html
The Play JSON example illustrates this problem well: matching on a JsArray populated with an IndexedSeq will yield unexpected results if you're not aware of the underlying Seq type.
underscore.iohttps://underscore.io/blog/posts/2020/05/14/porting-and-seq.html
Read at underscore.io
#scala-212 #scala-213 #pattern-matching #seq-type #play-json
[
|
]