> [...] unless you adopt a standard of never writing void functions. To be fair, that is a good principle to follow ;) Non-void, especially pure, functions are

> [...] unless you adopt a standard of never writing void functions. To be fair, that is a good principle to follow ;) Non-void, especially pure, functions are much easier to understand in the context of an entire codebase. > Ignoring an error-only return from a function doesn't produce a warning, It does if you use the standard set of linters, which with Go you almost certainly do. Go has a strong linting culture, in part due to one being built-in. By the way, in vscode said standard set of linters is one click away in the config. --- There are only 2-3 cases that I know of where failing to handle an error passes by silently. They are edge cases, not something you'll run into writing everyday code.