From a041d523de389b65b98a5373a8034041db2a8d83 Mon Sep 17 00:00:00 2001
From: Runxi Yu
Date: Thu, 2 Apr 2026 06:23:30 +0000
Subject: *: Remove

---
 internal/bufpool/buffer.go | 24 ------------------------
 1 file changed, 24 deletions(-)
 delete mode 100644 internal/bufpool/buffer.go

(limited to 'internal/bufpool/buffer.go')

diff --git a/internal/bufpool/buffer.go b/internal/bufpool/buffer.go
deleted file mode 100644
index b2d648a1..00000000
--- a/internal/bufpool/buffer.go
+++ /dev/null
@@ -1,24 +0,0 @@
-package bufpool
-
-// Buffer is a growable byte container that optionally participates in a
-// memory pool. A Buffer may be obtained through Borrow() or constructed
-// directly from owned data via FromOwned().
-//
-// A Buffer's underlying slice may grow as needed. When finished with a
-// pooled buffer, the caller should invoke Release() to return it to the pool.
-//
-// 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
-	buf  []byte
-	pool poolIndex
-}
-- 
cgit v1.3.1-10-gc9f91