Heads up, just published v0.11.14 of postcard-rpc, this adds a compile time check that catches cases of incorrect key calculation: https://github.com/jamesmunns/postcard-rpc/releases/tag/v0.11.14.... looking at your `const_cmp` impl (e.g. [this one](https://github.com/jamesmunns/postcard-rpc/blob/9281c63ec4edd9be8c73d627fac51b60bcf128ac/source/postcard-rpc/src/lib.rs#L244-L252)) and wondering: * shouldn't you check that `self.0.len() == other.0.len()`? * why the `let mut i = 0`, `while` and `i += 1` (which happens unconditionally) and not just `for i in 0..self.0.len()`? * why `all_match` and not just returning `false` on the first non-match (inversion of the `if` you currently have)?