From a88a96330f312d08f5d191c66a463b165ac1b96d Mon Sep 17 00:00:00 2001 From: Ariel Otilibili Date: Sun, 7 Dec 2025 00:39:34 +0000 Subject: [PATCH] cmd/cgo: use doc link for cgo.Handle Change-Id: If6af9842f563fe9233de0563d356e925a7b912f8 GitHub-Last-Rev: e8422e9a5aa9ca3140c96f7abfa4fa4482d709ab GitHub-Pull-Request: golang/go#76727 Reviewed-on: https://go-review.googlesource.com/c/go/+/727581 LUCI-TryBot-Result: Go LUCI Reviewed-by: David Chase Reviewed-by: Dmitri Shuralyov Reviewed-by: Ian Lance Taylor Reviewed-by: Sean Liao Auto-Submit: Sean Liao --- src/cmd/cgo/doc.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/cmd/cgo/doc.go b/src/cmd/cgo/doc.go index 7e8486874e..47d243d1a1 100644 --- a/src/cmd/cgo/doc.go +++ b/src/cmd/cgo/doc.go @@ -425,8 +425,8 @@ and of course there is nothing stopping the C code from doing anything it likes. However, programs that break these rules are likely to fail in unexpected and unpredictable ways. -The runtime/cgo.Handle type can be used to safely pass Go values -between Go and C. See the runtime/cgo package documentation for details. +The type [runtime/cgo.Handle] can be used to safely pass Go values +between Go and C. Note: the current implementation has a bug. While Go code is permitted to write nil or a C pointer (but not a Go pointer) to C memory, the -- 2.52.0