implement something similar to "go test".
I'm particularly intrigued by how you have blah_test.go, blah2_test.go and
they share a scope, can access blah.go (the package itself) but don't get
build as part of go build.
(purpose: adding some kind of blah_gen.go which is processed by a macro
engine and converted to a blah.go as a pre-build step)
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 firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.