You are not forced to handle errors. Or do you check for the errors returned by fmt.Print? I guess not.
This was my point: In many areas go forces the developer to the right thing (no unnecessary imports, gofmt...) and does not rely on developers discipline. But when i comes to error handling it does.
What i would wish for is some extended error handling supported by the compiler. I don't want a stack trace, but the compiler easily could produce for example a line number where the error was returned.
I'm using a small utility library to wrap the original error and add function name, line, file name and optionally a descriptive message that explains what failed.