go-linq VS jennifer

This is a lot more possible now that Go has generics (as of 1.18).

I would probably never use these, as I find such libraries are a whole new domain-specific language to learn, and often don't make things much simpler anyway, but here are some libraries where people have done something like this:

* https://github.com/ahmetb/go-linq: modelled after LINQ, but created pre-generics so only recently added some generics features

So awhile back, there was a port of Linq https://github.com/ahmetb/go-linq that ended up giving up, since then it has been continued with https://github.com/szmcdull/glinq

I am aware of this that predates generics: https://github.com/ahmetb/go-linq/blob/master/groupby.go

We have a repo/library called fasten-sources which is made up of mostly generated code (using dave/jennifer)

Check out my https://github.com/dave/rebecca package for a neat way of building readme docs by embedding Go docs and examples. It generates the readme for https://github.com/dave/jennifer (see https://github.com/dave/jennifer/blob/master/README.md.tpl).

The design of the wrapper functions meant we couldn’t easily unmarshal the CUE value into the wrapper functions. This meant we needed to generate unmarshalled functions for the config types. We use the excellent Jennifer library by Dave (no really; github.com/dave/jennifer) for generating Go files.

I've used https://github.com/dave/jennifer in the past, and been very happy with it.

If specifically for generating Go code, I would suggest you take a look at Jennifer.

I just spent a few hours writing a crapload of boilerplate code generation code with jennifer, if that helps any.