aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRob Findley <rfindley@google.com>2025-02-03 17:32:16 +0000
committerRobert Findley <rfindley@google.com>2025-02-03 10:04:00 -0800
commit9a107242109f6b426d14a89128de5f9d0878d85a (patch)
treeeaedb9b49b245289d58f037a2eed51d2a2c4835e
parent9d27ca2ee513b77cdf8415fc151f567a84617f1c (diff)
downloadgo-x-website-9a107242109f6b426d14a89128de5f9d0878d85a.tar.xz
_content/doc/go1.24.md: update printf analyzer documentation
Update the documentation for the new printf analyzer check, now that it only applies to 1.24 code. Change-Id: I92e718c52a6faaec7fc74b7763de295184430935 Reviewed-on: https://go-review.googlesource.com/c/website/+/646235 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Alan Donovan <adonovan@google.com>
-rw-r--r--_content/doc/go1.24.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/_content/doc/go1.24.md b/_content/doc/go1.24.md
index 9b00c616..d8e99a51 100644
--- a/_content/doc/go1.24.md
+++ b/_content/doc/go1.24.md
@@ -116,7 +116,10 @@ The existing `printf` analyzer now reports a diagnostic for calls of
the form `fmt.Printf(s)`, where `s` is a non-constant format string,
with no other arguments. Such calls are nearly always a mistake
as the value of `s` may contain the `%` symbol; use `fmt.Print` instead.
-See [#60529](/issue/60529).
+See [#60529](/issue/60529). This check tends to produce findings in existing
+code, and so is only applied when the language version (as specified by the
+go.mod `go` directive or `//go:build` comments) is at least Go 1.24, to avoid
+causing continuous integration failures when updating to the 1.24 Go toolchain.
<!-- go.dev/issue/64127 -->
The existing `buildtag` analyzer now reports a diagnostic when