polysemy-log-0.7.0.0: Polysemy effects for logging
Safe HaskellSafe-Inferred
LanguageHaskell2010

Polysemy.Log.Stdout

Description

 
Synopsis

Documentation

interpretDataLogStdoutWith :: Member (Embed IO) r => (a -> Text) -> InterpreterFor (DataLog a) r Source #

Interpret DataLog by printing to stdout, converting messages to Text with the supplied function.

interpretDataLogStdout :: Show a => Member (Embed IO) r => InterpreterFor (DataLog a) r Source #

Interpret DataLog by printing to stdout, converting messages to Text by using Show.

interpretLogStdoutWith :: Members [Embed IO, GhcTime] r => (LogEntry LogMessage -> Text) -> InterpreterFor Log r Source #

Interpret Log by printing to stdout, converting messages to Text with the supplied function.

interpretLogStdoutLevelWith :: Members [Embed IO, GhcTime] r => (LogEntry LogMessage -> Text) -> Maybe Severity -> InterpreterFor Log r Source #

Like interpretLogStdoutWith, but setting a log level. Nothing causes no messages to be logged.

interpretLogStdout :: Members [Embed IO, GhcTime] r => InterpreterFor Log r Source #

Interpret Log by printing to stdout, using the default formatter.

Since this adds a timestamp, it has a dependency on GhcTime. Use interpretLogStdout' for a variant that interprets GhcTime in-place.

interpretLogStdoutLevel :: Members [Embed IO, GhcTime] r => Maybe Severity -> InterpreterFor Log r Source #

Like interpretLogStdout, but setting a log level. Nothing causes no messages to be logged.

interpretLogStdout' :: Member (Embed IO) r => InterpreterFor Log r Source #

Interpret Log by printing to stdout, using the default formatter, then interpreting GhcTime.

interpretLogStdoutConc :: Members [Resource, Async, Race, Embed IO] r => InterpreterFor Log r Source #

Like interpretLogStdout, but process messages concurrently.