From f70130322cd306268c5da12c1517dc5725615ae8 Mon Sep 17 00:00:00 2001
From: Louis Pilfold <louis@lpil.uk>
Date: Thu, 15 Feb 2024 12:18:17 +0000
Subject: text -> en

---
 src/content/chapter5_advanced_features/lesson03_panic/en.html | 11 +++++++++++
 1 file changed, 11 insertions(+)
 create mode 100644 src/content/chapter5_advanced_features/lesson03_panic/en.html

(limited to 'src/content/chapter5_advanced_features/lesson03_panic/en.html')

diff --git a/src/content/chapter5_advanced_features/lesson03_panic/en.html b/src/content/chapter5_advanced_features/lesson03_panic/en.html
new file mode 100644
index 0000000..c54c217
--- /dev/null
+++ b/src/content/chapter5_advanced_features/lesson03_panic/en.html
@@ -0,0 +1,11 @@
+<p>
+  The <code>panic</code> keyword is similar to the <code>todo</code> keyword,
+  but it is used to crash the program when the program has reached a point that
+  should never be reached.
+</p>
+<p>
+  This keyword should almost never be used! It may be useful in initial
+  prototypes and scripts, but its use in a library or production application is
+  a sign that the design could be improved. With well designed types the type
+  system can typically be used to make these invalid states unrepresentable.
+</p>
-- 
cgit v1.2.3