From ae9938fae287606fb08395f4248393ea4acaa071 Mon Sep 17 00:00:00 2001
From: Robert Griesemer <gri@golang.org>
Date: Wed, 20 Nov 2024 12:50:54 -0800
Subject: [PATCH] doc: document new restriction on cgo-generated method
 receicer types

Follow-up on CL 629715.

For #60725.

Change-Id: I1b980ad44f73550b633c74fc881c70255e7d8565
Reviewed-on: https://go-review.googlesource.com/c/go/+/630335
Auto-Submit: Robert Griesemer <gri@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Reviewed-by: Robert Griesemer <gri@google.com>
TryBot-Bypass: Robert Griesemer <gri@google.com>
---
 doc/next/5-toolchain.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/next/5-toolchain.md b/doc/next/5-toolchain.md
index 04403eb550..05916531a1 100644
--- a/doc/next/5-toolchain.md
+++ b/doc/next/5-toolchain.md
@@ -1,5 +1,11 @@
 ## Compiler {#compiler}
 
+<!-- go.dev/issue/60725, go.dev/issue/57926 -->
+The compiler already disallowed defining new methods with receiver types that were
+cgo-generated, but it was possible to circumvent that restriction via an alias type.
+Go 1.24 now always reports an error if a receiver denotes a cgo-generated type,
+whether directly or indirectly (through an alias type).
+
 ## Assembler {#assembler}
 
 ## Linker {#linker}
-- 
2.48.1