async-bincode icon indicating copy to clipboard operation
async-bincode copied to clipboard

Asynchronous access to a bincode-encoded item stream.

Results 4 async-bincode issues
Sort by recently updated
recently updated
newest added

Was curious whether this relied on anything requiring an OS or if it could run on bare metal, specifically a wasm-unknown-unknown target. On the surface, it sounded like it just...

it's very hard to understand how to use this crate.

`bincode` allows limiting the memory usage of deserialized objects, and `async-bincode` should probably provide a facility for this as well. Without it, attackers are able to consume up to 8GB...

The previous behaviour caused the target buffer length to change between calls within a single read operation, which seems wrong since the underlying read would then try to read too...