4Pattern matching deconstructs a value to bring zero or more expressions into scope. Pattern matches are introduced with the `case` keyword.
6Pattern matches have the following general form::
13Pattern matching can also be used in the declaration of functions, as we have already seen::
15 fn pattern_1 ... pattern_n = result
17Patterns can also be used when introducing functions. For example::
19 example x y z = x * y + z
21The following pattern types are supported:
33Patterns need not be exhaustive. A pattern match failed exception will be thrown at runtime if no pattern matches the input.
38The wilcard `_` matches any input and brings nothing into scope::
45Literal patterns are provided to match on primitives::
59A variable pattern matches any input and binds that input to its name::
66Array patterns match an input which is an array, and bring its elements into scope. For example::
72Here, the first pattern only matches arrays of length one, and brings the first element of the array into scope.
74The second pattern matches arrays with two elements, and brings the first and second elements into scope.
79The head and tail of a non-empty array can be matched by using a cons pattern::
82 sum (x : xs) = x + sum xs
84`:` associates to the right::
86 addPairs (x : y : xs) = x * y + addPairs xs
93Constructor patterns match a data constructor and its arguments::
95 data Foo = Foo String | Bar Number Boolean
103Record patterns match an input which is a record, and bring its properties into scope::
105 f { foo = "Foo" } = o.bar
111The patterns above can be combined to create larger patterns. For example::
113 f { arr = x : _, take = "car" } = x
114 f { arr = _ : x : _, take = "cadr" } = x
120Named patterns bring additional names into scope when using nested patterns. Any pattern can be named by using the ``@`` symbol::
122 f a@(_ : _ : _) = true
125Here, in the first pattern, any array with two or more elements will be matched and bound to the variable ``a``.
130Guards are used to impose additional constraints inside a pattern using boolean-valued expressions, and are introduced with a pipe after the pattern::
133 evens (x : xs) | x % 2 == 0 = 1 + evens xs
134 evens (_ : xs) = evens xs
136When using patterns to define a function at the top level, guards appear after all patterns::
138 greater x y | x > y = true
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list