doc: describe how Zero optimization might change results of incorrect reflect.Value comparison
Update golang/go#33136
Update golang/go#43993
Change-Id: I306a8fd60a4d58cfd338edea4f21690338bf9a0b
Reviewed-on: https://go-review.googlesource.com/c/website/+/302269
Trust: Keith Randall <khr@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
diff --git a/_content/doc/go1.16.html b/_content/doc/go1.16.html
index ae122e6..79528d8 100644
--- a/_content/doc/go1.16.html
+++ b/_content/doc/go1.16.html
@@ -1090,6 +1090,19 @@
</dd>
</dl><!-- path/filepath -->
+<dl id="reflect"><dt><a href="/pkg/reflect/">reflect</a></dt>
+ <dd>
+ <p><!-- CL 192331 -->
+ The Zero function has been optimized to avoid allocations. Code
+ which incorrectly compares the returned Value to another Value
+ using == or DeepEqual may get different results than those
+ obtained in previous Go versions. The documentation
+ for <a href="/pkg/reflect#Value"><code>reflect.Value</code></a>
+ describes how to compare two <code>Value</code>s correctly.
+ </p>
+ </dd>
+</dl><!-- reflect -->
+
<dl id="runtime/debug"><dt><a href="/pkg/runtime/debug/">runtime/debug</a></dt>
<dd>
<p><!-- CL 249677 -->
