Hi - wondering whether anyone knows of any tooling that helps with 
"pipelines" (probably not a great choice of phrase) of go generate-able 
code. 

Specifically the case where the output of one go generate program is code 
which is itself go generate-able (and hence requires another invocation of 
go generate)

There are various strategies I can think of for handling this situation, 
but wanted to check if there was prior art out there before starting 
something home-baked.

Thanks,


Paul

-- 
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.

Reply via email to