summaryrefslogtreecommitdiffstats
path: root/site/posts/ExtensibleTypeSafeErrorHandling.org
diff options
context:
space:
mode:
Diffstat (limited to 'site/posts/ExtensibleTypeSafeErrorHandling.org')
-rw-r--r--site/posts/ExtensibleTypeSafeErrorHandling.org7
1 files changed, 6 insertions, 1 deletions
diff --git a/site/posts/ExtensibleTypeSafeErrorHandling.org b/site/posts/ExtensibleTypeSafeErrorHandling.org
index 9164bc2..0d40ed7 100644
--- a/site/posts/ExtensibleTypeSafeErrorHandling.org
+++ b/site/posts/ExtensibleTypeSafeErrorHandling.org
@@ -1,12 +1,17 @@
#+BEGIN_EXPORT html
<h1>Extensible Type-Safe Error Handling in Haskell</h1>
-<span class="time">February 04, 2018</span>
+<p>This article has originally been published on <span class="time">February 04,
+2018</span>.</p>
#+END_EXPORT
#+OPTIONS: toc:nil
#+TOC: headlines 2
+#+BEGIN_EXPORT html
+<div id="history">site/posts/ExtensibleTypeSafeErrorHandling.org</div>
+#+END_EXPORT
+
A colleague of mine introduced me to the benefits of [[https://crates.io/crates/error-chain][~error-chain~]], a crate which
aims to implement /“consistent error handling”/ for Rust. I found the overall
design pretty convincing, and in his use case, the crate really makes its error