(no title)
TwentyPosts | 1 year ago
The go devs decided against this since they didn't want to build a highly optimizing (read: slow) compiler, but that is missing the point of developer ergonomics.
TwentyPosts | 1 year ago
The go devs decided against this since they didn't want to build a highly optimizing (read: slow) compiler, but that is missing the point of developer ergonomics.
umanwizard|1 year ago
Most people nowadays ban building with warnings in CI and allow them during local development. But “CI” was barely a thing when go was developed so they just banned them completely. And now they are probably too stubborn to change.
yencabulator|1 year ago
https://go.dev/doc/faq#unused_variables_and_imports