Rudi Benkovič
Rudi Benkovič
`pub(crate)` didn't exist back then, so a bunch of things will have to be upgraded for this to work, but yes, for now, everything has to be public. You can...
This seems like a very niche problem, if there are more protocols like this in the wild (I've never encountered one) then I might be interested in this. Internally, all...
LSB integers with arbitrary bit widths are currently not supported as I haven't really encountered them in my usages. The first thing to precisely define and document would be the...
Hi, Unfortunately, type aliases are not supported in this way. A derive macro in Rust receives only the source of the particular struct, with no way to inspect the previously...
This actually compiles: ```rust pub type Field = MsbInteger; #[derive(PackedStruct)] #[packed_struct(bit_numbering="msb0")] pub struct S { #[packed_field(bits="0..", size_bits="4")] pub a: Field, #[packed_field(size_bits="4")] pub b: Field } ``` However those types were...
`bytes` and `bits` both specify the same thing, and it might be that `bytes` has priority here. Can you try it without `bytes`? This should also be an attribute-level error...
`BitOne` is not the right type to use here. `packed_bits::Bits1` would be the correct one. See the example at https://github.com/hashmismatch/packed_struct.rs/blob/master/packed_struct_tests/tests/packing_reserved.rs#L9 `bits` and `bytes` can be used interchangeably between fields, just...
Glad that you've found the library useful! I'd love to add support for floating points but I'll need to do some reading how various memory-constrained platforms and network protocols handle...
`u16` cannot be packed and unpacked from 2 bits, you need to wrap it with a type that fits into there. Following the example from the main README file, use...
The errors really aren't helpful, but it boils down to that we need to explicitly define the bit widths of every integer field so that the structures fields are protected...