Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

When discussing best practices for Go's error packages, the current examples define static sentinel errors using
fmt.Errorf().I believe this is undesirable for two reasons:
fmt.Errorf()without format verbs suggests formatting is occurring when it is not, causing readers to look for format verbs that do not exist.fmtis a large formatting package. For truly static errors, there is no reason to import it whenerrors.New()is designed for this use case.This change clarifies the separation of concerns:
errors.New()for static error declarations,fmt.Errorf()when formatting is actually needed.