proposal: x/exp/mmap: expose a File-like type #39683
Labels
Milestone
Comments
andybons
changed the title
|
Is there a reason you can't (or shouldn't) wrap it in an |
|
no, I just didn't think about but for "application B", I would need r/w capabilities (to interact with a Cyclone V FPGA board) |
|
You could easily fork SectionReader and create SectionWriter. Writing to a fixed area is not particularly common though, so it might not be worth putting in io itself. It does seem like the general adapters are better than more functionality in package mmap itself. |
|
Based on the discussion above, this seems like a likely decline. |
|
No change in consensus, so declined. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
right now, with the current
mmap.ReaderAttype, one can easily (and from multiple goroutines) access mmap'ed data.that's great.
but my application A also needs an
io.Reader.I've resorted to forking the
x/exp/mmappackage under go-mmap/mmap, that exposes aReadertype that implementsio.Reader,io.Seeker,io.ReaderAtandio.ByteReader.now, in yet another application (B), to interface with a FPGA board, I'd also need write access.
it comes to reason to thus expose a
File-like type, implementing alsoio.Writer,io.WriterAtandio.ByteWriter.The text was updated successfully, but these errors were encountered: