From 8f2c36a2da5c8cbf599723d386d358c363de06d9 Mon Sep 17 00:00:00 2001 From: Robert Krzyzanowski Date: Fri, 10 Apr 2015 23:03:11 -0500 Subject: [PATCH] fix typo --- content/exceptions-best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/exceptions-best-practices.md b/content/exceptions-best-practices.md index 1f1cc3c..7cee5cc 100644 --- a/content/exceptions-best-practices.md +++ b/content/exceptions-best-practices.md @@ -101,7 +101,7 @@ f :: SomeVal -> SomeVal -> SomeVal -> Either F'sExceptionType F'sResult ``` The problem is that these types don't unify. Also, it's commonly the case that -we really don't need to about *why* a lookup failed, we just need to deal with +we really don't need to know about *why* a lookup failed, we just need to deal with it. For those cases, `Maybe` is better. The solution to this is the `MonadThrow` typeclass from the exceptions package.