rnd
The table for historical entries lists the brightness value as uint32 value but only mentions the bytes 7 to 9 with 10 as a padding byte while its actually part...
Same request as #2 i just accidentally closed the other one as I deleted my branch inside the fork. --- This is the necessary template change to make ctron/rust-esp-template#1 work.
The current version of `esp32-sys` is required to simulate the existance of `std::os::raw` as the bindings are generated without the `--cyptes-prefix` flag. Without this flag any libc related types are...
Right now this draft only parameterizes the decoding part to ensure the given structure matches the expectations of @thequux. I am going to implement the encoding part as soon as...
The current display message is defined as https://github.com/P3KI/bendy/blob/92c6e07493e5bd61d605e59430067edda7e7f3e7/src/decoding/error.rs#L52 but based on the usage in https://github.com/P3KI/bendy/blob/92c6e07493e5bd61d605e59430067edda7e7f3e7/src/decoding/error.rs#L90-L95 it should be the other way around.
This pull requests introduces a new `StateTracker` trait, based on the public interface of the old `StateTracker` struct. To avoid any naming clashes the old struct got renamed into `StrictTracker`....
If [cfg(doctest)](https://github.com/rust-lang/rust/issues/62210) stabilized (or `cfg(test)` got fixed), we can use [doc-comment](https://crates.io/crates/doc-comment) for including code in `README` in doc-test, then we can remove `tests/readme.rs`.
The port of additional test cases (#20) to fix issue #7 revealed a new question. The original test suite contained some cases marked as "illegal" which contain more tokens than...
**What?** Add a flag to enable/disable the parsing of non-canonical input. **How?** Make the decoder parameterized on the state tracker.