>The following line in golang ignores the error:

   fmt.Println("foo")

    a := func() error {
        return nil 
    }
    a()

    go-lint: Error return value of 'a' is not checked (errcheck)

    res, err := foo("foo")
    if err != nil { ... }
    if res != nil { ... }
    res, err = foo("bar")
    if res != nil { ... }

    go-lint: ineffectual assignment to 'err' (ineffassign)

That's the issue with the language, there are so many special cases for convenience sake, not for correctness sake. It's obvious why it's excluded, but it doesn't make it correct. Do you want critical software written in such a language?

Furthermore, does that linter work with something like gorm (https://gorm.io/) and its way of handling errors? It's extremely easy to mis-handle errors with it. It's even a widely used library.