That doesn't really make sense? The module cache is for immutable versions of modules, ie. publish your (generated) code as a package/module, import that it will then get cached
On Tuesday, October 20, 2020 at 8:50:25 PM UTC+2 mattm...@gmail.com wrote: > Hey folks, > > I'm working on a project with a lot of code generation. I'd love to: > > - get the code generation out of the way when you don't care about it > - be able to vendor the generated code when you do care about it > > That led me to an idea about generating code into the go module cache. Do > you see any downside in doing this? > > Thanks! > Matt > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/69e3f7d7-fede-4d78-b6b1-e745a4466e79n%40googlegroups.com.
