Add support for unused/padding bits about deku HOT 4 CLOSED

I'm thinking the naming skip could be used for something else, for example:

struct SomeStruct {
    #[deku(bits = "6")]
    field_a: u8,

    #[deku(skip, map = "to_string(field_a)" )]
    field_a_as_string: String,

    field_b: u8,
}

If a user really wanted to "skip", the user could specify a custom reader/writer, would that be sufficient? These types of utility functions could be provided by deku, i.e.

struct SomeStruct {
    #[deku(bits = "6")]
    field_a: u8,

    #[deku(reader = "deku::utils::skip_x_bits(2)", writer = "")]
    _unused: u8,

    field_b: u8,
}

from deku.

Alternatively, ignore might be a good name

struct SomeStruct {
    #[deku(bits = "6")]
    field_a: u8,

    #[deku(ignore, bits = "2")]
    _unused: u8,

    field_b: u8,
}

from deku.

Would this be possible?

struct SomeStruct {
    #[deku(bits = "6")]
    field_a: u8,
    #[deku(ignore, bits = "2")]
    field_b: u8,
}

Where 6 bits are read, then 2 are ignored, then 8 are read for u8. Without a dummy struct field.

from deku.

Would this be possible?

struct SomeStruct {
    #[deku(bits = "6")]
    field_a: u8,
    #[deku(ignore, bits = "2")]
    field_b: u8,
}

Where 6 bits are read, then 2 are ignored, then 8 are read for u8. Without a dummy struct field.

@wcampbell0x2a, it may be possible yes. It is required to have a field though. Just to expand on the example, something like this could be interesting, not sure if they're combined or not... needs experimentation

struct SomeStruct {
    #[deku(bits = "6")]
    field_a: u8,
    #[deku(ignore, bits = "2")]
    #[deku(bits = "6")]
    field_b: u8,
}

from deku.