Dmitrii Kovanikov

I'm not sure about adding more functions that work with `LoggerT`. I wouldn't want to invest in this interface more. With time, it became clear that `LoggerT` brings more problems...

@qwbarch As I mentioned before, if you only use `WithLog` constraint, it could be better to just pass `LogAction` explicitly like this: ```haskell zeroM :: Monad m => LogAction m...

Hi @alaendle! Thanks for the idea 👍🏻 I don't think we should change the time zone for "local time" by default. Usually, you have logs enabled on multiple deployed environments,...

Hi @alaendle, sorry for the delays in my replies. I'm currently in the process of splitting the old `co-log` repo into separate packages and I'm on the `co-log` itself at...

@qnikst I remember, you had some ideas regarding structured logging. Will you have time to share your thoughts? :slightly_smiling_face:

Hi @ashutoshrishi, thanks for your feedback! I've created a separate [issue about supporting logging without colouring](https://github.com/kowainik/co-log/issues/183). I think it should be solved independently from this one.

@qnikst Thanks for sharing your experience and ideas with regards to structured logging. It is handy for us to design a flexible and extensible interface. It'll take some time to...

@yaitskov That's an interesting idea. Logging and tracing are indeed similar in some sense. `co-log` is very flexible due to underlying concepts in its core, and supporting tracing shouldn't be...

@avanov The amount of required effort is not that big if you want something simple :slightly_smiling_face: The only thing we need to finish this is more time. Unfortunately, free time...

I think we can reuse `typerep-map` for this problem as well. But this will be possible only after this issue is done: * https://github.com/kowainik/typerep-map/issues/53 Currently we have: ```haskell data Message...