logging-effect 1.3.9 → 1.3.10

raw patch · 3 files changed

+19/−3 lines, 3 filesdep ~basePVP ok

version bump matches the API change (PVP)

Dependency ranges changed: base

API changes (from Hackage documentation)

+ Control.Monad.Log: instance Control.Monad.IO.Unlift.MonadUnliftIO m => Control.Monad.IO.Unlift.MonadUnliftIO (Control.Monad.Log.DiscardLoggingT msg m)

Files

Changelog.md +9/−0
logging-effect.cabal +2/−2
src/Control/Monad/Log.hs +8/−1

Changelog.md view

@@ -1,3 +1,12 @@+## Unreleased++### Other changes++* Add MonadUnliftIO instance to DiscardLoggingT+* Support `base-4.14`++---+ ## 1.3.9 -- 2020-01-25  ### Other Changes

logging-effect.cabal view

@@ -1,5 +1,5 @@ name: logging-effect-version: 1.3.9+version: 1.3.10 synopsis: A mtl-style monad transformer for general purpose & compositional logging homepage: https://github.com/ocharles/logging-effect license: BSD3@@ -13,7 +13,7 @@ library   exposed-modules:     Control.Monad.Log   other-extensions:    ViewPatterns, OverloadedStrings, GeneralizedNewtypeDeriving, FlexibleContexts, FlexibleInstances, MultiParamTypeClasses, FunctionalDependencies, PatternSynonyms-  build-depends:       base >=4.8 && <4.14+  build-depends:       base >=4.8 && <4.15                      , async >=2.0 && <2.3                      , transformers >=0.4 && <0.6                      , text >=1.2 && <1.3

src/Control/Monad/Log.hs view

@@ -630,6 +630,13 @@   liftBaseWith runInBase = lift (liftBaseWith (\runInOrig -> runInBase (runInOrig . discardLogging)))   restoreM = lift . restoreM +instance MonadUnliftIO m => MonadUnliftIO (DiscardLoggingT msg m) where+  askUnliftIO =+    DiscardLoggingT+      $ withUnliftIO+      $ \u ->+        return (UnliftIO (unliftIO u . discardLogging))+ instance MonadTrans (DiscardLoggingT message) where   lift = DiscardLoggingT   {-# INLINEABLE lift #-}@@ -653,7 +660,7 @@ Unlike other logging libraries available on Hackage, 'MonadLog' does /not/ assume that you will be logging text information. Instead, the choice of logging data is up to you. This leads to a highly compositional form of logging, with-the able to reinterpret logs into different formats, and avoid throwing+the ability to reinterpret logs into different formats, and avoid throwing information away if your final output is structured (such as logging to a relational database).