|| at Mar 19, 2014 at 3:30 pm
Hmmm, I was unaware of the bug in gc. I had certainly noticed that there
was an impact on compile times. In any case, this approach has the
advantage of being a pure Go solution without any odd compiler or linker
steps, which certainly makes it useful (i.e. for app engine).
I've mentioned it in other threads, I believe that given the importance
that the Go team has placed on easy distribution of statically compiled
executables, there should be a tool to do the above included in the
On Tuesday, 18 March 2014 21:55:23 UTC-4, Stephen Gutekanst wrote:
You should be careful how often you do this, it can greatly slow down
compile times and increase the memory required to build your application.
 go-wiki: GcToolchainTricks<https://code.google.com/p/go-wiki/wiki/GcToolchainTricks
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 email@example.com.
For more options, visit https://groups.google.com/d/optout.