xerrors: undeprecate Errorf Message about deprecation of `xerrors.Errorf` may confuse people because they will think that `fmt.Errorf` will work the same way. In fact, fmt.Errorf will not capture a stack backtrace. Change-Id: I912f6b2ef289e97e69fe21160af62ba1ef4aa0a5 GitHub-Last-Rev: 16289f933ca8f83195e309c932b58850053c1504 GitHub-Pull-Request: golang/xerrors#3 Reviewed-on: https://go-review.googlesource.com/c/xerrors/+/410314 Reviewed-by: Ian Lance Taylor <iant@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Ian Lance Taylor <iant@google.com>
diff --git a/fmt.go b/fmt.go index 6df1866..27a5d70 100644 --- a/fmt.go +++ b/fmt.go
@@ -34,7 +34,8 @@ // operand that does not implement the error interface. The %w verb is otherwise // a synonym for %v. // -// Deprecated: As of Go 1.13, use fmt.Errorf instead. +// Note that as of Go 1.13, the fmt.Errorf function will do error formatting, +// but it will not capture a stack backtrace. func Errorf(format string, a ...interface{}) error { format = formatPlusW(format) // Support a ": %[wsv]" suffix, which works well with xerrors.Formatter.