is it possible to provide an 'unsafe' way to get internal []byte and avoid mem copy?

[codingWhat]

What is the issue you are having?

In some scenarios, the data retrieved from the cache will not be modified and could be directly returned.

What is BigCache doing that it shouldn't?

func readEntry(data []byte) []byte {
	length := binary.LittleEndian.Uint16(data[timestampSizeInBytes+hashSizeInBytes:])

	// copy on read
	dst := make([]byte, len(data)-int(headersSizeInBytes+length))
	copy(dst, data[headersSizeInBytes+length:])

	return dst
}

to be --- to recycle the 'dst'

func readEntry(dst, data []byte) []byte {
	length := binary.LittleEndian.Uint16(data[timestampSizeInBytes+hashSizeInBytes:])

	copy(dst, data[headersSizeInBytes+length:])

	return dst
}

[janisz]

That makes sense, so we could include Unsafe get methods. I'm curious about the best way to approach this. Instead of modifying the existing bigcache interface, maybe we could create an alternative implementation, like UnsafeBigCache, where all method signatures would remain unchanged. 🤔

However, there’s a downside to consider: this approach might lead to unintended effects when data is overwritten without a way to notify the user.

Also, I'm wondering why we need to copy to dst — can’t we just return data[headersSizeInBytes+length:] directly?

[codingWhat]

I totally agree with you .

I think adding a GetWithUnsafe is enough, and any user who calls this method must take responsibility for data security and ensure that it is not modified.

look forward to this enhancement..😄