On Fri, Nov 5, 2021 at 5:10 AM Alberto Donizetti
wrote:
> Could be due to https://github.com/golang/go/issues/48496
> Should be fixed on tip, but 1.17 is affected.
>
>
Thanks for this pointer. I just tested this and it made a huge difference.
For a change to a single file, compiling on 1.17.2 tak
On Thu, Nov 4, 2021 at 10:25 AM Brian Hatfield wrote:
> This seems a little like you might have a background compilation process
> occurring which is populating the build cache. What editor environment are
> you using? Is it possible it is effectively running compilations on your
> code, whether
I recently migrated from a 2019 i9 Macbook Pro to a new M1 Max Macbook Pro
(64GB on both machines), and to my surprise, my go build times ended up
being the same. I started to do some research, and I've found a curious
behavior that I'm hoping someone can shed some light on. This is with go
1.1
