aboutsummaryrefslogtreecommitdiff
path: root/src/content/chapter5_advanced_features/lesson03_panic/en.html
diff options
context:
space:
mode:
Diffstat (limited to 'src/content/chapter5_advanced_features/lesson03_panic/en.html')
-rw-r--r--src/content/chapter5_advanced_features/lesson03_panic/en.html11
1 files changed, 0 insertions, 11 deletions
diff --git a/src/content/chapter5_advanced_features/lesson03_panic/en.html b/src/content/chapter5_advanced_features/lesson03_panic/en.html
deleted file mode 100644
index c54c217..0000000
--- a/src/content/chapter5_advanced_features/lesson03_panic/en.html
+++ /dev/null
@@ -1,11 +0,0 @@
-<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>