The implementation of pattern matching in Scala 3 was greatly simplified compared to Scala 2. From a user perspective, this means that Scala 3 generated patterns are a lot easier to debug, as variables all show up in debug modes and positions are correctly preserved.
Scala 3 supports a superset of Scala 2 extractors.
Boolean MatchU =:= Boolean
0
patternsFor example:
object Even:
def unapply(s: String): Boolean = s.size % 2 == 0
"even" match
case s @ Even() => println(s"$s has an even number of characters")
case s => println(s"$s has an odd number of characters")
// even has an even number of characters
Product Match
U <: Product
N > 0
is the maximum number of consecutive (val
or parameterless def
) _1: P1
... _N: PN
members in U
N
patterns with types P1, P2, ..., PN
For example:
class FirstChars(s: String) extends Product:
def _1 = s.charAt(0)
def _2 = s.charAt(1)
// Not used by pattern matching: Product is only used as a marker trait.
def canEqual(that: Any): Boolean = ???
def productArity: Int = ???
def productElement(n: Int): Any = ???
object FirstChars:
def unapply(s: String): FirstChars = new FirstChars(s)
"Hi!" match
case FirstChars(char1, char2) =>
println(s"First: $char1; Second: $char2")
// First: H; Second: i
Single Match
1
pattern with type S
For example, where Nat <: R
, S = Int
:
class Nat(val x: Int):
def get: Int = x
def isEmpty = x < 0
object Nat:
def unapply(x: Int): Nat = new Nat(x)
5 match
case Nat(n) => println(s"$n is a natural number")
case _ => ()
// 5 is a natural number
Name-based Match
S
has N > 1
members such that they are each val
s or parameterless def
s, and named from _1
with type P1
to _N
with type PN
S
doesn't have N+1
members satisfying the previous point, i.e. N
is maximalN
patterns with types P1, P2, ..., PN
For example, where U = AlwaysEmpty.type <: R
, S = NameBased
:
object MyPatternMatcher:
def unapply(s: String) = AlwaysEmpty
object AlwaysEmpty:
def isEmpty = true
def get = NameBased
object NameBased:
def _1: Int = ???
def _2: String = ???
"" match
case MyPatternMatcher(_, _) => ???
case _ => ()
Sequence Match
V <: X
type X = {
def lengthCompare(len: Int): Int // or, `def length: Int`
def apply(i: Int): T1
def drop(n: Int): scala.Seq[T2]
def toSeq: scala.Seq[T3]
}
T2
and T3
conform to T1
N
simple patterns with types T1, T1, ..., T1
, where N
is the runtime size of the sequence, or>= N
simple patterns and a vararg pattern (e.g., xs: _*
) with types T1, T1, ..., T1, Seq[T1]
, where N
is the minimum size of the sequence.For example, where V = S
, U = Option[S] <: R
, S = Seq[Char]
object CharList:
def unapplySeq(s: String): Option[Seq[Char]] = Some(s.toList)
"example" match
case CharList(c1, c2, c3, c4, _, _, _) =>
println(s"$c1,$c2,$c3,$c4")
case _ =>
println("Expected *exactly* 7 characters!")
// e,x,a,m
Product-Sequence Match
V <: Product
N > 0
is the maximum number of consecutive (val
or parameterless def
) _1: P1
... _N: PN
members in V
PN
conforms to the signature X
defined in Seq Pattern>= N
patterns, the first N - 1
patterns have types P1, P2, ... P(N-1)
, the type of the remaining patterns are determined as in Seq Pattern.For example, where V = S
, U = Option[S] <: R
, S = (String, PN) <: Product
, PN = Seq[Int]
class Foo(val name: String, val children: Int*)
object Foo:
def unapplySeq(f: Foo): Option[(String, Seq[Int])] =
Some((f.name, f.children))
def foo(f: Foo) = f match
case Foo(name, x, y, ns*) => ">= two children."
case Foo(name, ns*) => "< two children."
There are plans for further simplification, in particular to factor out product match and name-based match into a single type of extractor.
Type testingAbstract type testing with ClassTag
is replaced with TypeTest
or the alias Typeable
.
_: X
for an abstract type requires a TypeTest
in scopex @ X()
for an unapply that takes an abstract type requires a TypeTest
in scopeRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4