doc/go1.18: add caution about use of generics in production

Per https://groups.google.com/g/golang-dev/c/iuB22_G9Kbo/m/7B1jd1I3BQAJ.

For #47694

Change-Id: I033cdadb2067e432f7c307d1546b4c5d0cfd5d8c
Reviewed-on: https://go-review.googlesource.com/c/go/+/371954
Trust: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Robert Griesemer <gri@golang.org>

1 files changed, 15 insertions, 0 deletions

diff --git a/doc/go1.18.html b/doc/go1.18.html
index e156f21eb2..64481a1466 100644
--- a/doc/go1.18.html
+++ b/doc/go1.18.html
@@ -32,10 +32,25 @@ Do not send CLs removing the interior tags from such phrases.
   <a href="https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md">Type
     Parameters Proposal</a>.
   This includes major - but fully backward-compatible - changes to the language.
+</p>
+
+<p>
+  These new language changes required a large amount of new code that
+  has not had significant testing in production settings. That will
+  only happen as more people write and use generic code. We believe
+  that this feature is well implemented and high quality. However,
+  unlike most aspects of Go, we can't back up that belief with real
+  world experience. Therefore, while we encourage the use of generics
+  where it makes sense, please use appropriate caution when deploying
+  generic code in production.
+</p>
+
+<p>
   The following is a list of the most visible changes. For a more comprehensive overview, see the
   <a href="https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md">proposal</a>.
   For details see the <a href="https://golang.org/ref/spec">language spec</a>.
 </p>
+
 <ul>
   <li>
     The syntax for