failable 1.2.0.0 → 1.2.0.1
raw patch · 2 files changed
+36/−2 lines, 2 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
Files
- failable.cabal +3/−2
- package.yaml +33/−0
failable.cabal view
@@ -4,10 +4,10 @@ -- -- see: https://github.com/sol/hpack ----- hash: 0abe156a52880d8108f2cd1ead2a01df5ab9adf98e83877eb4a53ed83789fab7+-- hash: 1e63a61c70483d7525dbe87ed02e180668b9ff7107e8fd8c94524e24a739df96 name: failable-version: 1.2.0.0+version: 1.2.0.1 synopsis: A 'Failable' error monad class to unify failure across monads that can fail description: This library contains a 'Failable' error monad class to unify failure across monads and transformers most commonly used to implement pipelines that can fail and does so in a simple nonsense way by providing the means of signaling a computation "failure" while striving to keep the failure behaviour consistent with the actual definition of the monad/transformer. Please refer to the README file for a more elaborate description and some examples. category: control, exceptions, monad@@ -21,6 +21,7 @@ extra-source-files: README.md ChangeLog.md+ package.yaml source-repository head type: git
+ package.yaml view
@@ -0,0 +1,33 @@+name: failable+version: 1.2.0.1+license: BSD3+author: "Erick Gonzalez"+maintainer: "erick@codemonkeylabs.de"+copyright: "2019 Erick Gonzalez"+git: https://gitlab.com/codemonkeylabs/failable+bug-reports: https://gitlab.com/codemonkeylabs/failable/issues++extra-source-files:+- README.md+- ChangeLog.md+- package.yaml++# Metadata used when publishing your package+# synopsis: Short description of your package+# category: Web++# To avoid duplicated efforts in documentation and dealing with the+# complications of embedding Haddock markup inside cabal files, it is+# common to point users to the README.md file.+synopsis: A 'Failable' error monad class to unify failure across monads that can fail+description: This library contains a 'Failable' error monad class to unify failure across monads and transformers most commonly used to implement pipelines that can fail and does so in a simple nonsense way by providing the means of signaling a computation "failure" while striving to keep the failure behaviour consistent with the actual definition of the monad/transformer. Please refer to the README file for a more elaborate description and some examples.++category: control, exceptions, monad++dependencies:+- base >= 4.8 && < 5+- mtl >= 2.2 && < 2.3+- transformers >= 0.4.2 && < 0.6++library:+ source-dirs: src