Go runtime: 4 years later

Re:Go runtime: 4 years later by randomdata on Tuesday September 27, 2022 @10:47AM (#32995960)

Fast compilation times are a human-centric goal. The machine couldn't care less if it takes a millennia to compile your program. Only humans care about fast compile times.

But, I'm not sure that is even the primary benefit. The primary benefit is that you won't be incentivized to leave unused imports and variables to litter your code, as I see happen all the time in languages that aren't so strict. The Go team has even stated that they decided there would be no warnings because they've learned that warnings get ignored.

[ Parent | on HN ]

Re:Go runtime: 4 years later by peterashford on Wednesday September 28, 2022 @01:27AM (#33004535)

they could have had a flag for people who prefer those issues to be warnings. for me, they slow my debugging down a great deal

[ Parent | on HN ]

Re:Go runtime: 4 years later by bayindirh on Wednesday September 28, 2022 @03:16AM (#33005103)

Then most (if not all) Go programs wouldn’t compile without that flag.

If something can be abused, it’s going to be abused.

[ Parent | on HN ]