From 6fa0aeff4b735ddfb4bcd4c526275899e54cb082 Mon Sep 17 00:00:00 2001
From: Daniel Lemire <daniel@lemire.me>
Date: Mon, 16 Sep 2024 13:57:16 -0400
Subject: [PATCH] doc: fix comment

---
 roaring.go | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/roaring.go b/roaring.go
index 2f5f78b8..c7f00af1 100644
--- a/roaring.go
+++ b/roaring.go
@@ -289,8 +289,7 @@ func (rb *Bitmap) Checksum() uint64 {
 // copy-on-write which means that modifying them creates copies. Thus FromUnsafeBytes is more likely to be appropriate for read-only use cases,
 // when the resulting bitmap can be considered immutable.
 //
-// See also the FromBuffer function: most users should prefer FromBuffer unless the need the performance,
-// and are aware of the implications of holding references to the input data buffer.
+// See also the FromBuffer function. We recommend benchmarking both functions to determine which one is more suitable for your use case.
 // See https://github.com/RoaringBitmap/roaring/pull/395 for more details.
 func (rb *Bitmap) FromUnsafeBytes(data []byte, cookieHeader ...byte) (p int64, err error) {
 	stream := internal.NewByteBuffer(data)