Well, no. Go gets compiled to one binary. A developer of another package can’t influence your binary by just changing their code. Also adding an error as a return value changes the signature of a function. If this happens in a library your code depends on, your code won’t even compile until you’ve modified it to deal with the error.

Go’s error handling is one of its greatest strengths. Rather than in languages that throw exceptions, go forces you to consider the possible ways things could go wrong. This means that it is much easier to write resiliant projects in go.