relude VS co-log

I've also hoped that the "standard library" (i.e. Prelude) should be redesigned. I just found relude which looks very promising.

Project to look at is: https://github.com/kowainik/relude.

Another good practice to prevent runtime exceptions is to avoid partial functions like head and tail. One way to ensure that one doesn't accidentally slip in is to use an alternative prelude (e.g. relude) that doesn't export them by default. Another alternative is to use hlint to warn about them (and then import their safe counterparts instead).

That note is wrong, it is only a problem if the function input has a large cardinality. I opened a PR to fix this: https://github.com/kowainik/relude/pull/389

And relude.

Another great Kowainik project to suggest is co-log: https://github.com/co-log/co-log

We use co-log it is simple and extensible, and can easily be integrated.

That being said, the fact that you're trying to define an instance of HasLog for ActionT in the first place is a bit suspect, since this co-log tutorial suggests you shouldn't need to do anything of the sort. I think you should be able to perform logging in your App and then lift the App to ActionT by using ActionT's MonadTrans instance. That is, something like this: