The reason I am trying to avoid using a code generator is because it isn't integrated into VScode. I write a small section of code, then I write tests that I have set to show logging output, so I can quickly figure out when something is wrong. Code generation adds a lot of manual work to this.
Personally I prefer to just work with the base toolset. I don't like glide, I don't like makefiles. I seriously doubt that passing functions back to the base library incurs that much of a cost. But that was along the lines I was thinking, I discovered go generate yesterday also but it looked to me like it was just a tool to speed up building out the function stubs from interfaces and not for replacing a particular string. Well, I could always use sed, but it's just another thing to debug. I want to get this thing finished, as I have been chipping away on it for nearly 2 months... On Friday, 4 May 2018 07:41:19 UTC+3, Tamás Gulácsi wrote: > > Without generics, the usual solution is code generation. There are several > helper utilities, but you can create your own, too. > Write one version with a specific type, and replace it with the concrete > one. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
