ref: 36ca8828cb5fb76a2a9b6c821f7d7ca18e9e83bc
parent: 0ea0365280b99e91a045115b96720dc28309604b
author: Runxi Yu <me@runxiyu.org>
date: Sun Feb 22 04:51:18 EST 2026
bufpool: Document how .Bytes is intended to be used
--- a/internal/bufpool/buffers.go
+++ b/internal/bufpool/buffers.go
@@ -25,6 +25,12 @@
// Buffers must not be copied after first use; doing so can cause double-returns
// to the pool and data races.
//
+// In general, pass Buffer around when used internally, and directly .Bytes() when
+// returning output across our API boundary. It is neither necessary nor efficient
+// to copy/append the .Bytes() to a newly-allocated slice; in cases where we do
+// want the raw byte slice out of our API boundary, it is perfectly acceptable to
+// simply not call Release().
+//
//go:nocopy
type Buffer struct { _ struct{} // for nocopy--
⑨