jam1garner
jam1garner
General idea is providing a module containing both a custom parser and a custom writer function. This would also make it easier to make binrw compatibility crates by allowing you...
Todo: - [x] Document end-user ability to use reference types - [x] Document limitations regarding manual lifetime specification (eg to use `'_`) - [x] Better document how manual `BinRead` implementations...
For a while I've wanted this, but haven't made an issue until now as I want to have it ready by 0.9.0's release. Things needed: * [x] landing page *...
See the following comment: https://github.com/jam1garner/binrw/issues/7#issuecomment-930539560
If you miss a `count` attribute on a Vec right now you get the following: ``` error[E0277]: the trait bound `VecArgs: Default` is not satisfied --> src/segment.rs:34:10 | 34 |...
Alright, you've all seen this before: ``` | 3 | #[derive(BinWrite { .. })] | ++++++ ``` rustc thinks some code binrw generates is causing an error due to some...
Similar to #75, errors relating to improperly passing arguments can be confusing to binrw beginners due to the fact all the named types currently have no/minimal documentation. The goal of...
* [x] Cleanup binread derive code * [ ] no_std std::io reimplementation * [x] Error * [x] Result * [ ] Buffering types? * [ ] BufReader * [ ]...