Alexander Vershilov

> What was the conclusion of this investigation? I think I didn't come with a concrete solution, but I can't recall since long time passed. > I think it would...

Let me add my few cents here. So I've implemented structured logging based on co-log for my project, but the solution is specific for my needs and I'm not sure...

With regards to concrete actions that can be done in oder to provide general support for the structured logging, I'd do the following: Introduce new package `co-log-structured` with minimal set...

@avanov for what it worth I've managed to open source an [implementation](https://github.com/cheopslab/cheops-logger/tree/master/co-log-json) I've described above. It still need some polishing, documentation and introducing examples, and possible interface generalisation. So I...

@avanov, I've released a package https://hackage.haskell.org/package/co-log-json. Feel free to use and contribute to :)

So assume the following queries with `hasql` ```Haskell example1 :: HS.Statement Int64 Entry example1 = HS.Statement sql encoder decoder False where sql = "select id, name, phone from book where...

It will definitely solve the issue as I will be able to do some post processing before creating my type. And it looks like a nice function to have. However...

For me it has not that nice ergonomics but it allows to solve the problem. So we can consider this issue resolved.

Yes, as usual, 3 version support, 7.10 may survive until it compiles but no longer, for the older versions we should just do not allow that.

Yes will try to do that today.