bitf
Rust procedural macro to quickly generate bitfield from a structure.
Usage and syntax
The macro can be used as following:
#[bitf(size)]
OR
#[bitf(size, order)]
Where size can be:
u8
u16
u32
u64
u128
And order can be 'lsb' or 'msb'
The size parameter will constrain the total size of the bitfield.
The order parameter is optional and will alter the order in which the fields are declared.
By default this parameter is set to lsb.
When setting the order parameter to msb, the first declared field of the struct will be set on the most significant bit, and the other way around when using the lsb mode.
Hence, the size and position of the field is based on the field declaration :
use bitf;
// The internal, full value of the field can be accessed as :
let e = default;
println!;
When combined to other attributes, make sure to implement it BEFORE any #[derive(..)] attribute, or the expansion order might (will) fail.
use bitf;
Skipping the implementation of a field
You can use the following syntax when declaring a field to skip its implementation.
_reserved_intSize
In the previous example, the field _reserved_4 will not have its 4 bits implemented.
No accessor will be generated for this field.
Example
Considering the following bitfield:
7 0
0 0 0 0 0 0 0 0
| | | | | | | |_ field_a - Size 1
| | | | | | |___ fieldB - Size 1
| | | | | |_____ fieldC - Size 1
| | \|/________ reserved - Size 3
\ /_____________ field_D - Size 2
It can be achieved with the following declaration and macro usage
use bitf;
This will generate the following structure and associated methods
//So you can easily set and read values of each defined bitfield:
let mut bf = default;
bf.set_field_a;
bf.set_fieldB;
println!;
TODO
- A short-sighted decision made it that currently the macro is assuming that the format of the declared field is of the form CamelCaseName_Size. Would be better to implement the form Any_Case_Size
- Generate proper rust documentation
- Implement a pretty print for easy bitfield reading
- Skip the implementation of the fields defined as reserved (or not?). Done: you can mark a field as reserved using the naming convention `_reserved_intSize
- Implement a check to fail if the bitfield is too small to hold every declared field
- Add lsb/msb as optional param, make lsb default
- Add visibility modifier param. Either all declared field are implemented as pub (default) or specified by user
- Add custom return type for each declared field
- Support the addition of attribute to the structure