Support for Span<byte>

[Ricochet73]

I use the CircularBuffer for some R&D work. I have some blittable structs message types, and marshalling to byte sequences. Currently I use Span, but because writing to a buffer requires byte[] I need to create a byte array, which means making a copy of the bytes, I want to try and reduce this and thought it would be nice fi the library natively supported Span to avoid the copying needed to create an array.

[Ricochet73]

As a side note, I use zero copy marshalling as the struct maps directly to the byte sequence.

[justinstenning]

Absolutely it needs to support Spans (they didn't exist yet when this was written)

[Ricochet73]

That was a quick response! Yes, spans were not available then. Will you look at this at some point?

[justinstenning]

I don't have a lot of time at the moment, so not sure when I'll get to it, you can probably get away with using Memory spans and the IntPtr, not sure yet

[Ricochet73]

no worries, I'll see if I can get it to work in the source. It is not urgent, just trying to squeeze out a little more performance.

…

On Sun, 23 Feb 2025 at 08:51, Justin Stenning ***@***.***> wrote: I don't have a lot of time at the moment, so not sure when I'll get to it, you can probably get away with using Memory spans and the IntPtr, not sure yet — Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFI6DNICND2FOWUVR4NRMDL2RFVW3AVCNFSM6AAAAABXV67G6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZWGY3DANZVGI> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: justinstenning]*justinstenning* left a comment (justinstenning/SharedMemory#75) <#75 (comment)> I don't have a lot of time at the moment, so not sure when I'll get to it, you can probably get away with using Memory spans and the IntPtr, not sure yet — Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFI6DNICND2FOWUVR4NRMDL2RFVW3AVCNFSM6AAAAABXV67G6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZWGY3DANZVGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>