From f22ec51debeddc0903096e66bfaf641568bede3b Mon Sep 17 00:00:00 2001
From: Dan Scales <danscales@google.com>
Date: Sat, 22 May 2021 13:40:20 -0700
Subject: [PATCH] doc: add Go 1.17 release note about inlining functions with
 closures

Fixes #45781

Change-Id: Ia5bc2845f7f94aff4f3f0ff15533feb148223adb
Reviewed-on: https://go-review.googlesource.com/c/go/+/322089
Trust: Dan Scales <danscales@google.com>
Reviewed-by: Cherry Mui <cherryyz@google.com>
---
 doc/go1.17.html | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/doc/go1.17.html b/doc/go1.17.html
index 6dd1d0d1db..c2317a4035 100644
--- a/doc/go1.17.html
+++ b/doc/go1.17.html
@@ -228,7 +228,14 @@ Do not send CLs removing the interior tags from such phrases.
 
 <h2 id="compiler">Compiler</h2>
 
-<p>
+<p><!-- CL 283112, golang.org/issue/28727 -->
+
+  Functions containing closures can now be inlined. One effect of this change is
+  that a function with a closure may actually produce a distinct closure function
+  for each place that the function is inlined. Hence, this change could reveal
+  bugs where Go functions are compared (incorrectly) by pointer value. Go
+  functions are by definition not comparable.
+
   TODO: complete the Compiler section, or delete if not needed
 </p>