Sorry, maybe cache is the wrong word. Wherever "go get -u ..." downloads modules, I'd like to stick my generated code.
Conceptually you could think of it as a virtual module used only during development. If you're familiar with Node.js, You could also think of it as creating a directory in node_modules/ and then importing it with require(...). I'm just wondering if I'll run into issues doing this or mess up other people's modules. On Tuesday, October 20, 2020 at 9:22:05 PM UTC+2 seank...@gmail.com wrote: > 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/a26c4aca-bbe3-4dc5-9f66-09d1db521517n%40googlegroups.com.
