From c2dcbe0f25a3e8bd60a4ccf377bbdd47f4794871 Mon Sep 17 00:00:00 2001
From: Louis Pilfold <louis@lpil.uk>
Date: Tue, 26 Mar 2024 13:57:31 +0000
Subject: Document opaque types

Closes https://github.com/gleam-lang/language-tour/issues/63
---
 src/content/chapter5_advanced_features/lesson03_panic/en.html | 11 -----------
 1 file changed, 11 deletions(-)
 delete 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
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>
-- 
cgit v1.2.3