aboutsummaryrefslogtreecommitdiff
path: root/src/content/chapter5_advanced_features/lesson04_let_assert/en.html
diff options
context:
space:
mode:
Diffstat (limited to 'src/content/chapter5_advanced_features/lesson04_let_assert/en.html')
-rw-r--r--src/content/chapter5_advanced_features/lesson04_let_assert/en.html15
1 files changed, 0 insertions, 15 deletions
diff --git a/src/content/chapter5_advanced_features/lesson04_let_assert/en.html b/src/content/chapter5_advanced_features/lesson04_let_assert/en.html
deleted file mode 100644
index 29fd06c..0000000
--- a/src/content/chapter5_advanced_features/lesson04_let_assert/en.html
+++ /dev/null
@@ -1,15 +0,0 @@
-<p>
- <code>let assert</code> is the final way to intentionally crash your Gleam
- program. It is similar to the <code>panic</code> keyword in that it crashes
- when the program has reached a point that should never be reached.
-</p>
-<p>
- <code>let assert</code> is similar to <code>let</code> in that it is a way to
- assign values to variables, but it is different in that the pattern can be
- <i>partial</i>. The pattern does not need to match every possible value of the
- type being assigned.
-</p>
-<p>
- Like <code>panic</code> this feature should be used sparingly, and likely not
- at all in libraries.
-</p>