diff options
Diffstat (limited to 'src/content/chapter2_flow_control/lesson02_variable_patterns/text.html')
| -rw-r--r-- | src/content/chapter2_flow_control/lesson02_variable_patterns/text.html | 17 |
1 files changed, 3 insertions, 14 deletions
diff --git a/src/content/chapter2_flow_control/lesson02_variable_patterns/text.html b/src/content/chapter2_flow_control/lesson02_variable_patterns/text.html index b3e4000..7e9ac11 100644 --- a/src/content/chapter2_flow_control/lesson02_variable_patterns/text.html +++ b/src/content/chapter2_flow_control/lesson02_variable_patterns/text.html @@ -1,18 +1,7 @@ <p> - The case expression is the most common kind of flow control in Gleam code. It - is similar to <code>switch</code> in some other languages, but more powerful - than most. + Patterns in case expressions can also assign variables. </p> <p> - It allows the programmer to say "if the data has this shape then run this - code", a process called called <em>pattern matching</em>. -</p> -<p> - Gleam performs <em>exhaustiveness checking</em> to ensure that the patterns in - a case expression cover all possible values. With this you can have confidence - that your logic is up-to-date for the design of the data you are working with. -</p> -<p> - Try commenting out patterns or adding new redundant ones, and see what - problems the compiler reports. + When a variable name is used in a pattern the value that is matched against is + assigned to that name, and can be used in the body of that clause. </p> |