With that many deps, the linking numbers could be expected, Go 1.7 improves this significantly.
I cannot explain the compilation time for the package. I recommend waiting til the end of the day and upgrading to Go 1.7 as it us unlikely that any fix for this will be backported to Go1.6.x On Tuesday, 16 August 2016 07:43:41 UTC+10, James Pettyjohn wrote: > > No, it's some hundreds of strings across that whole package, none longer > than 100 characters. No giant static XML strings or the like. > > Thinking it might be telling to see dependency information I ran into > (your) articles on golang dependency tools > <http://dave.cheney.net/2014/11/21/visualising-dependencies>, so if it's > of any note: > > go list -f '{{ join .Imports "\n" }}' site_www2 | wc -l > 93 > go list -f '{{ join .Deps "\n" }}' site_www2 | wc -l > 257 > > Don't know that this is very telling. > > Is there another important metric as far as go compilation? Or another > compiler option to see numbers branches or the like which could point up > something? > > > On Monday, August 15, 2016 at 1:40:19 PM UTC-7, Dave Cheney wrote: >> >> That looks like the case. >> >> Do you include a large amount of static data in the site_www2 package? >> > -- 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.
