bytes.Buffer.ReadAt?

[fri...@gmail.com]

Is there a reason I shouldn't submit a PR for bytes.Buffer.ReadAt?  It would at least help for some in memory tests.

--

Thanks,

fREW

[roger peppe]

The reason bytes.Buffer doesn't implement io.ReaderAt is that it doesn't keep bytes in the buffer that have been read, so it's not possible to implement that method.

You can use bytes.Reader instead, which does implement io.ReaderAt and io.Seeker.

To make a bytes.Reader from a bytes.Buffer, you can do `bytes.NewReader(buf.Bytes())`.

  hope this helps,

    rog.

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[fREW Schmidt]

Oh thanks, I'll switch my code to reader, though as far as I can tell,
bytes.Buffer doesn't discard already read data, it merely sets the
(private) offset. Maybe I just got luck though.

Thanks again!

--
fREW Schmidt
https://blog.afoolishmanifesto.com

[Thomas Bushnell, BSG]

Notice the logic in (*bytes.Buffer).grow which will throw away already read data, specifically in the case n <= c/2--m.

[fREW Schmidt]

Ah my stuff just never got that big. Thank you!