On Sun, Dec 18, 2016 at 3:45 AM, Saurabh Nanda <saurabhnanda@gmail.com> wrote:
if I don't understand why I'm unable to catch errors in MonadIO I'm bound to get stuck again, or implement it incorrectly (for example, what are the resource leaks that were being referred to?)
 
https://mail.haskell.org/pipermail/libraries/2014-November/024224.html is the start of the rather large thread that led to the current exception primitives, which exception managers ranging from the standard `bracket` to MonadBaseControl rely on. There are quite a few examples of resource leaks during exception handling (or despite exception handling!) in it, along with many other pitfalls that can occur.

--
brandon s allbery kf8nh                               sine nomine associates
allbery.b@gmail.com                                  ballbery@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net