#bit-fields #bit #macro #struct #generate #version #ipv4

bitfield

This crate provides macros to generate bitfield-like struct

26 unstable releases (8 breaking)

Uses old Rust 2015

0.17.0 Sep 8, 2024
0.16.1 Jul 25, 2024
0.14.0 Jul 11, 2022
0.13.2 May 27, 2019
0.0.1 Nov 20, 2014

#42 in Rust patterns

Download history 76963/week @ 2024-08-23 81171/week @ 2024-08-30 81452/week @ 2024-09-06 73840/week @ 2024-09-13 76622/week @ 2024-09-20 67755/week @ 2024-09-27 65342/week @ 2024-10-04 72356/week @ 2024-10-11 80331/week @ 2024-10-18 75488/week @ 2024-10-25 81037/week @ 2024-11-01 73971/week @ 2024-11-08 78421/week @ 2024-11-15 81341/week @ 2024-11-22 75358/week @ 2024-11-29 62850/week @ 2024-12-06

311,801 downloads per month
Used in 1,594 crates (110 directly)

MIT/Apache

48KB
682 lines

rust-bitfield

This crate provides macros to generate bitfield-like struct.

This a complete rewrite of the bitfield crate. You can find the previous version in the rust-bitfield-legacy repository. This version works on the stable version of rustc and use a different syntax with different possibility.

Example

An IPv4 header could be described like that:

bitfield!{
    struct IpV4Header(MSB0 [u8]);
    u32;
    get_version, _: 3, 0;
    get_ihl, _: 7, 4;
    get_dscp, _: 13, 8;
    get_ecn, _: 15, 14;
    get_total_length, _: 31, 16;
    get_identification, _: 47, 32;
    get_df, _: 49;
    get_mf, _: 50;
    get_fragment_offset, _: 63, 51;
    get_time_to_live, _: 71, 64;
    get_protocol, _: 79, 72;
    get_header_checksum, _: 95, 79;
    get_source_address, _: 127, 96;
    get_destination_address, _: 159, 128;
}

In this example, all the fields are read-only, the _ as setter name signals to skip the setter method. The range at the end (e.g. 3, 0) defines the bit range where the information is encoded.

Documentation

The documentation of the released version is available on doc.rs.

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

No runtime deps