aboutsummaryrefslogtreecommitdiff
path: root/lessons/src/lesson023_variable_patterns/text.html
diff options
context:
space:
mode:
Diffstat (limited to 'lessons/src/lesson023_variable_patterns/text.html')
-rw-r--r--lessons/src/lesson023_variable_patterns/text.html17
1 files changed, 0 insertions, 17 deletions
diff --git a/lessons/src/lesson023_variable_patterns/text.html b/lessons/src/lesson023_variable_patterns/text.html
deleted file mode 100644
index 8154979..0000000
--- a/lessons/src/lesson023_variable_patterns/text.html
+++ /dev/null
@@ -1,17 +0,0 @@
-<p>
- The case expression is the most common kind of flow control in Gleam code. It
- is similar to `switch` in some other languages, but more powerful than most.
-</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.
-</p>