The features of Go's error handling that people don't like aren't necessary to achieve that. In any language that requires a function to declare in its signature whether it can err (either through result types or through checked exceptions), code coverage tooling should be able to detect and report all untested error cases.

That said, I'm not sure whether actually existing coverage tools for those languages do this. I'll check and see if I can find out.