From afe675c2fa9deacd61f5684be54f1ebbdc94fc0c Mon Sep 17 00:00:00 2001
From: Russ Cox <rsc@golang.org>
Date: Thu, 20 Oct 2016 14:37:31 -0400
Subject: [PATCH] doc/faq: mention that copying discussion is semantics, not
 implementation

Fixes #17181.

Change-Id: If7cc4865e391acf76512f7ec7167d5a31377b598
Reviewed-on: https://go-review.googlesource.com/31574
Reviewed-by: Rob Pike <r@golang.org>
---
 doc/go_faq.html | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/go_faq.html b/doc/go_faq.html
index 6a955f6f3f..37a31ae289 100644
--- a/doc/go_faq.html
+++ b/doc/go_faq.html
@@ -1151,6 +1151,12 @@ struct.  If the interface value holds a pointer, copying the interface value
 makes a copy of the pointer, but again not the data it points to.
 </p>
 
+<p>
+Note that this discussion is about the semantics of the operations.
+Actual implementations may apply optimizations to avoid copying
+as long as the optimizations do not change the semantics.
+</p>
+
 <h3 id="pointer_to_interface">
 When should I use a pointer to an interface?</h3>
 
-- 
2.48.1