Oops, ended up writing a couple of paragraphs about ways we could possibly better support writing and reading numbers with endianness from the Read/Write traits:https://github.com/async-rs/async-std/issues/578 …
-
-
The approach I've always used is "fill the buffer as much as possible, then parse". There can be an API above verifying that there's enough data, but it's a bad idea to tie it to IO, that's too low level: most protocols define the format and the IO behaviour
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.
Personally I'm a bit worried of the overhead of doing an await for each little part of e.g. a parser, but maybe that's actually small? And I hope people will not await directly on sockets but buffered reader/writer adapters