tree c8baa05f41c405f95bde03564a73466599b8342a
parent fb4f8c1d3a179654f93ef7e91d68fc7b1de6e88f
author Leonel Quinteros <leonel.quinteros@gmail.com> 1520341521 +0000
committer Andrew Bonventre <andybons@golang.org> 1520453522 +0000

lint: avoid false positives with custom errors-package

When using `errors.New(fmt.Sprintf(...))`,
lint will alert that you should use `fmt.Errorf(...)`.

Before this patch, this alert was also displayed
when using a custom errors-package.
There are valid use cases to use `errors.New(fmt.Sprintf(...))`
in a custom errors-package context.

This patch avoids the "false positive" alert
when a custom errors-package is imported in the current file.

Fixes golang/lint#350

Change-Id: I7cc82a3435b184f8b4cad0752a75d44f33536dce
GitHub-Last-Rev: ad257d26802aca316d6b83758fcb143083934587
GitHub-Pull-Request: golang/lint#360
Reviewed-on: https://go-review.googlesource.com/96091
Reviewed-by: Andrew Bonventre <andybons@golang.org>