failable 0.1.0.2 → 0.1.0.3

raw patch · 3 files changed

+4/−4 lines, 3 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• README.md +1/−1
• failable.cabal +2/−2
• src/Control/Monad/Failable.hs +1/−1

@@ -9,7 +9,7 @@  I am sure a lot of ink has been spilled in forums and around water coolers all around the world,  debating the merits and fallacies of one approach or the other. The reason for this package is not-to participate in this discussion but rather to provide a simple nonsense means of signaling a +to participate in this discussion but rather to provide a simple no nonsense means of signaling a  computation "failure" in those monads that provide the inherent means to do so, and to do it in a consistent manner 

@@ -4,10 +4,10 @@ -- -- see: https://github.com/sol/hpack ----- hash: 017ba691ee87716cab21fcf1f65adf24ca7da1417e8abac7aaf260871f21716d+-- hash: bf2c314c1ef35bb95db8c0f1d14aa05f8b2da20a6e76dace01662f21847ee451  name:           failable-version:        0.1.0.2+version:        0.1.0.3 synopsis:       A 'Failable' error monad class to unify failure across monads that can fail description:    Please see the README on Gitlab at <https://gitlab.com/codemonkeylabs/failable#readme> category:       control, exceptions, monad

@@ -15,7 +15,7 @@ -- | -- I am sure a lot of ink has been spilled in forums and around water coolers all around the -- world, debating the merits and fallacies of one approach or the other. The reason for this--- package is not to participate in this discussion but rather to provide a simple nonsense+-- package is not to participate in this discussion but rather to provide a simple no nonsense -- means of signaling a computation "failure" in those monads that provide the inherent means -- to do so, and to do it in a consistent manner. --