Could be due to https://github.com/golang/go/issues/48496 Should be fixed on tip, but 1.17 is affected.
Alberto On Thursday, 4 November 2021 at 18:44:01 UTC+1 Mark Fletcher wrote: > On Thu, Nov 4, 2021 at 10:25 AM Brian Hatfield <bmhat...@gmail.com> 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 via IDE support, indirectly via linters, or other on-save >> actions? >> >>> >>> > Hmm, well I think you're right. I use VSCode, which runs gopls. It never > occured to me that gopls would run a compile, but I guess in hindsight it > makes sense. If I shut down VSCode and instead edit the file using vi, I > get consistent 16 second compile times regardless of how long I wait. So, > thanks for the suggestion. I still don't understand why my compile times > are the same between the i9 and M1 Max, but I guess I need to do some more > research. > > Thanks, > Mark > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/924f99e0-9cb0-4614-bd71-4d4fbfd263adn%40googlegroups.com.
