Use Go 1.18 generics over "genny"

[lukasmalkmus]

What is your take on Go 1.18 generics? Is that something you plan to support or implement? This would replace genny.

[kelindar]

Most definitely, I want to get rid of my genny fork and let compiler do its thing.

[lukasmalkmus]

Do you mind me bringing up a branch and trying some stuff out over the holidays? Would love to play around with the beta and have a proper use case. Will also get some benchmarks. Even if it won't get accepted we might get some insights from it.

[lukasmalkmus]

And I didn't know you were using your own genny fork. Might want to tag it using tools.go.

[kelindar]

Do you mind me bringing up a branch and trying some stuff out over the holidays? Would love to play around with the beta and have a proper use case. Will also get some benchmarks. Even if it won't get accepted we might get some insights from it.

Of course, would be great

[lukasmalkmus]

I weren't able to implement anything usable yet, however, when using your genny fork I noticed it procudes different code than the one checked in manually. For example the casing is different and the generated code has "go:build ignore" tags.