Add "No exception handling?" article

Author: alvinng4

content/docs/API/error_types.mdx

@@ -5,8 +5,11 @@ title: Error and Warning Types
 # Error and Warning Types
 
 Inspired by Python, we provide the following error and
-warning hierarchy. It is for reference only as we decided
-not to implement exceptions catching.
+warning hierarchy. 
+
+<Callout type="info">It is for reference only as we decided
+not to implement exceptions catching.<br />
+See [No exception handling?](../articles/exception_handling)</Callout>
 
 ## Error Hierarchy
 To throw an error with a type below, add CTB as prefix and turn it into

content/docs/API/throwing_errors.mdx

@@ -148,7 +148,8 @@ Clear all recorded errors.
 ```c
 void ctb_clear_error(void);
 ```
-<Callout type="warning">This function is not recommended as exception handling is not formally supported</Callout>
+<Callout type="warning">This function is not recommended as exception handling is not formally supported.<br />
+See [No exception handling?](../articles/exception_handling)</Callout>
 
 ### `ctb_dump_traceback` <Badge text="Function" />
 Dump the traceback of all recorded errors to stderr and clear errors.

content/docs/articles/exception_handling.mdx

@@ -0,0 +1,16 @@
+---
+title: No exception handling?
+---
+
+# No exception handling?
+
+While we support the `Try` part in try/catch, we do not support `Catch` for multiple reasons:
+
+1. To support try and catch, we would need an error stack that could extends to arbitrary depth. However, for the following reasons,
+we decided to use a fixed amount of memory for the error stack:
+    * **Safety**
+    * Reduce complexity of our implementation
+2. C doesn't have exceptions handling, so adding catch would force users to learn a new way to write C, which is bad and makes our library over-complicated for users.
+3. You may be tempted to use `ctb_clear_error()` to do exceptions catching. It could be dangerous 
+if you have some previous errors that you forgot to handle, especially when we are not a language-level framework
+to enforce error checking and exiting.