From f208bf8cb11e792e6c8411990995939117265016 Mon Sep 17 00:00:00 2001
From: Brad Fitzpatrick <bradfitz@tailscale.com>
Date: Mon, 6 Oct 2025 08:23:11 -0700
Subject: [PATCH] types/lazy: document difference from sync.OnceValue

Updates #8419
Updates github.com/golang#62202

Change-Id: I0c082c4258fb7a95a17054f270dc32019bcc7581
Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>
---
 types/lazy/lazy.go | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/types/lazy/lazy.go b/types/lazy/lazy.go
index f5d7be494..f537758fa 100644
--- a/types/lazy/lazy.go
+++ b/types/lazy/lazy.go
@@ -23,6 +23,9 @@ var nilErrPtr = ptr.To[error](nil)
 // Recursive use of a SyncValue from its own fill function will deadlock.
 //
 // SyncValue is safe for concurrent use.
+//
+// Unlike [sync.OnceValue], the linker can do better dead code elimination
+// with SyncValue. See https://github.com/golang/go/issues/62202.
 type SyncValue[T any] struct {
 	once sync.Once
 	v    T