Dmitrii Kovanikov

I finally found an acceptable solution to this problem! Since GHC 9.0 we can use `QualifiedDo` to have a fast and type-safe interface. The obvious monoid I was looking for...

@vrom911 Good question. For quite some time I was thinking about implementing our own time formatting. Since we don't need a lot of flexibility, we can provide the fastest timestamp...

@pangwa I agree that having an example of logging rotation would be good. I've added it to the list (and I see that you've also opened a separate issue and...

Currently waiting for this feature in `colourista`: https://github.com/kowainik/colourista/issues/26

Hi @epicallan! Thanks for your support and desire to help :blush: I would really prefer to base the solution on `colourista`, and we are currently working on implementing support for...

@jacobstanley thanks for your suggestion! It would be indeed great to have many instances. However, this is tricky. > MonadReader `LoggerT` already implements `MonadReader` instance for `LogAction` and `MonadReader` typeclass...

Hi @ArulselvanMadhavan! I like the `streamly` package, and I would love to help with the smoother integration of `co-log` with `streamly`. I think it's better to continue discussion under a...

Improvements to benchmarks implemented by @vrom911 in #114 show that performance of encoding `RichMessage` to `ByteString` doesn't affect performance of logging that much. But maybe if we change formatting from...

@vrom911 I noticed that in your PR #166 you worked with `Builder` directly instead of appending just `Text`. If my understanding is correct, appending `Builder`s is much more efficient than...

My gut feeling says that `ByteString` builder is better. Usually `IO` with `ByteString` is much more reliable and faster. And there's even a function that can output a `Builder` directly...