Thanks for the feedback.
> You would need to write the programs go generate is calling to be > idempotent, and have the second one exit quietly if the first hasn't run. > You would then either run go generate twice or have the first program run > go generate once it had completed. > Regarding such go generate programs needing to be idempotent. I was planning on using a simple hashing strategy similar to that used in gt ( https://github.com/rsc/gt); go generate would then be called as many times as required on a package until a fixed point hash is reached. This obviates the need for any go generate program to know about any other, or where any such program may sit in any given pipeline. Clearly a simple strategy for not executing infinitely can be introduced in case things go "wrong" Not pretty but it does seem like a rare case. To be honest, I'd probably > use a Makefile instead of go generate. > I'm quite happy with the semantics as described by `go generate --help`. All I think I need is a simple wrapper to automate this pipeline approach and make it non-project specific; for us it's come up in a couple of places, but admittedly never more than a two-step pipeline. -- 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.
