Is there any value in me reporting it? If helpful, I may be able to toss a large tarball up on Dropbox or something. It's not really high priority for me either tbh because I know it would be difficult to stream the compilation inside the same package w/ circular refs and therefore may not be fixed for years. Thanks for your help.
On Tuesday, January 10, 2017 at 11:35:32 AM UTC-6, Ian Lance Taylor wrote: > > On Tue, Jan 10, 2017 at 9:22 AM, <chad...@gmail.com <javascript:>> > wrote: > > > > Just as an update, Go 1.8 doesn't help much, and the compile flags do > reduce > > memory usage which only extends the inevitable time it runs out of > memory. I > > guess I am at a loss here. I suppose this is not considered a bug, > correct? > > Just a practical limitation of the compiler to use more memory > proportional > > to same-package code size? > > Oh, no, it's definitely a bug. It's just very hard to fix and rare in > practice, so it's not high priority. > > Ian > -- 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.
