doc/go1.17: mention new possibility of type conversion panicking

For #44513
For #46020

Change-Id: I07c7a4268465c536d1866cc6bb1fad76b2b88b15
Reviewed-on: https://go-review.googlesource.com/c/go/+/326149
Trust: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Matthew Dempsky <mdempsky@google.com>

diff --git a/doc/go1.17.html b/doc/go1.17.html
index cc3bcdf1801f6426f79ca5f888c7c496e163aa26..011377a84e739c0dec8c1aa67feb5de3d7392320 100644 (file)
--- a/doc/go1.17.html
+++ b/doc/go1.17.html
@@ -67,6 +67,14 @@ Do not send CLs removing the interior tags from such phrases.
   using <code>unsafe.Add</code> or <code>unsafe.Slice</code>.
 </p>
 
+
+<p>
+  Note that the new conversion from slice to array pointer is the
+  first case in which a type conversion can panic at run time.
+  Analysis tools that assume type conversions can never panic
+  should be updated to consider this possibility.
+</p>
+
 <h2 id="ports">Ports</h2>
 
 <h3 id="darwin">Darwin</h3>