From 4efb34bd728732101432843ed0bfbeb971272287 Mon Sep 17 00:00:00 2001
From: Louis Pilfold <louis@lpil.uk>
Date: Thu, 21 Dec 2023 14:03:41 +0000
Subject: Add chapters

---
 .../lesson02_variable_patterns/text.html                | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 src/content/chapter2_flow_control/lesson02_variable_patterns/text.html

(limited to 'src/content/chapter2_flow_control/lesson02_variable_patterns/text.html')

diff --git a/src/content/chapter2_flow_control/lesson02_variable_patterns/text.html b/src/content/chapter2_flow_control/lesson02_variable_patterns/text.html
new file mode 100644
index 0000000..8154979
--- /dev/null
+++ b/src/content/chapter2_flow_control/lesson02_variable_patterns/text.html
@@ -0,0 +1,17 @@
+<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>
-- 
cgit v1.2.3