aboutsummaryrefslogtreecommitdiff
path: root/src/content/chapter2_flow_control/lesson01_case_expressions/en.html
diff options
context:
space:
mode:
authorLouis Pilfold <louis@lpil.uk>2024-02-15 12:18:17 +0000
committerLouis Pilfold <louis@lpil.uk>2024-02-19 18:18:04 +0000
commitf70130322cd306268c5da12c1517dc5725615ae8 (patch)
tree2f047d58f0bd0c9438d57b42499d40d13fea73ad /src/content/chapter2_flow_control/lesson01_case_expressions/en.html
parent63120914512bd4a3003788a7592ef3cc4ff32cf5 (diff)
downloadtour-f70130322cd306268c5da12c1517dc5725615ae8.tar.gz
tour-f70130322cd306268c5da12c1517dc5725615ae8.zip
text -> en
Diffstat (limited to 'src/content/chapter2_flow_control/lesson01_case_expressions/en.html')
-rw-r--r--src/content/chapter2_flow_control/lesson01_case_expressions/en.html18
1 files changed, 18 insertions, 0 deletions
diff --git a/src/content/chapter2_flow_control/lesson01_case_expressions/en.html b/src/content/chapter2_flow_control/lesson01_case_expressions/en.html
new file mode 100644
index 0000000..07ff421
--- /dev/null
+++ b/src/content/chapter2_flow_control/lesson01_case_expressions/en.html
@@ -0,0 +1,18 @@
+<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.
+</p>
+<p>
+ It allows the programmer to say "if the data has this shape then run this
+ code", a process 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>