All Versions
7
Latest Version
Avg Release Cycle
-
Latest Release
-
Changelog History
Changelog History
-
v0.2.2 Changes
mtl-compat
now uses automatic flags instead of manual ones. This has a number of benefits:- There is no need for making several simultaneous releases to support each flag combination.
- As a result, the
cabal-install
constraint solver should have a much easier time figuring out install-plans involvingmtl-compat
.
Due to old
cabal-install
bugs,cabal-install-1.16
and older may have a harder time installing this package, so it is recommended that you usecabal-install-1.18
or later. (Or, if you must usecabal-install-1.16
or older, installingmtl-compat
with the appropriate flags should help.) -
v0.2.1 Changes
- ๐
Require use of
transformers-compat-0.4
or greater when building withmtl-2.1.3.1
or earlier.transformers-compat-0.4.0.*
adds the missingExceptT
instances, which means thatmtl-compat
's only purpose is to backport theControl.Monad.Except
module for those who want anmtl
-style import forExceptT
and/orMonadError
.
I would recommend just using
Control.Monad.Trans.Except
fromtransformers-compat-0.4.0.*
andControl.Monad.Error.Class
instead, since they accomplish the same thing asmtl-compat
without an extra dependency. - ๐
Require use of
-
v0.2.1.3 Changes
- ๐ A specific build with no flags explicitly enabled, intended for use with the latest version of
mtl
. This is a workaround forcabal
backtracker bugs.
- ๐ A specific build with no flags explicitly enabled, intended for use with the latest version of
-
v0.2.1.2 Changes
- ๐ A specific build with the
-ftwo-point-two
flag explicitly enabled. This is a workaround forcabal
backtracker bugs.
- ๐ A specific build with the
-
v0.2.1.1 Changes
- ๐ A specific build with the
-ftwo-point-one
flag explicitly enabled. This is a workaround forcabal
backtracker bugs.
- ๐ A specific build with the
-
v0.1.1 Changes
- ๐ Allowed the
two-point-one
flag to toggle on/off automatically
- ๐ Allowed the
-
v0.1 Changes
- ๐ Initial commit