Wondering which extensions to the Read / Write trait would be needed to reproduce 80% of what Nom does. Probably should actually *try* nom first, but got a vague suspicion a few key additions would get us there? https://docs.rs/nom/5.0.1/nom/
You mean don't pass `impl Read` as a parameter to a parser? Or more like: "don't be bound to e.g. TcpStream"? I like the traits in params, but def agree on not tying to specific IO impls.
-
-
Nah Geoffroy means full-on state machines haha
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I write protocol impls that work on buffers: it's easy to make them deterministic and they can fit nicely in either sync or async contexts, either with raw evented or wrapped in futures
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
