There are lots of tools in Go that make up for issues people have with the language. Another example is the IDE macros people use for the standard if err != nil {} block.
> Another example is the IDE macros people use for the standard if err != nil {} block
Which doesn't make code easy to read when there are 10th of these blocks in a single function.
This may be considered cheating since it isn't baked into the language but there are tools to do this at build time, here's one: https://github.com/kisielk/errcheck