Hacker News new | ask | show | jobs
by dgellow 1975 days ago
You have go-lint or other linters to enforce it. It’s a per-project choice.
1 comments

It's either a "per-project/leave it to the linter" choice, or a "they did this in the language to force people to handle errors close to the source".

Can't have it both ways!

The “force” is the part that is incorrect, or at least misleading. The go approach is to encourage people to handle it at the call site, and you can use extra tooling to enforce it.

Once you get that point, there is no contradiction.