Provide buffer parser i.e. `runParserPtr :: ParserIO e a -> Ptr Word8 -> Int -> _`

Brief preamble. I'm using flatparse for some binary file parsing. I'm parsing a filetable, where I know the precise length. I'm operating on Ptrs because I want the core to be source-agnostic (whether working on bytestrings directly, or file handles etc.). I could copy the bytes into a bytestring and parse, but I figure, why don't I parse an address directly? To my (limited) knowledge, it would seem sensible, assuming the lifetime is handled externally (e.g. using withForeignPtr).

Assuming good intentions (no lying about pointers or their length), would a runParserPtr :: ParserIO e a -> Ptr Word8 -> Int -> _ be useful and safe? With lots of warnings on pitfalls of course.

I can provide some example code if useful.

Start by reviewing the existing ParserIO API and how parser inputs and lifetimes are currently handled. Determine whether a pointer-and-length entry point can be specified with safe lifetime and bounds expectations; done requires a decided API design, documented pitfalls, and corresponding implementation or a clear resolution that it is not safe or useful.