Robin Freyler

Yeah so I guess I have to implement parsing. But never mind, I have already implemented some parsers in the past so it should be all right. Thank you very...

Hi! Can you please make an example of your use case? I wonder, would it be possible to just define this trait on your side and simply implement it for...

Okay I got your use case. But couldn't you simply write your own `Bitfield` trait and simply implement this `Bitfield` trait for all your concrete bitfield types? I should be...

Yes, you need to add `filled = false` since you do not fill all the available bits in your `#[bitfield]`. ```rust #[bitfield(specifier = true, filled = false)] #[derive(Copy, Clone, PartialEq,...

Well I don't know why but it compiles completely fine on my machine. :upside_down_face: ```rust use modular_bitfield::prelude::*; #[bitfield(specifier = true)] #[derive(Copy, Clone, PartialEq, Debug)] #[cfg_attr(feature = "serde", derive(serde::Deserialize, serde::Serialize))] pub...

I toyed some more and now also stubled upon your error. It can be triggered with `cargo clippy` which is why `cargo build` and `cargo run` worked for me. Seems...

With the ability to use `#[derive(BitfieldSpecifier)]` on a `#[bitfield]` struct which implements the `Specifier` trait which is probably what this issue asks for: Is there still a need for this...

> Seems like I have the same: > > ```rust > #[bitfield(bits = 64, filled = false)] > #[derive(Debug, BitfieldSpecifier)] > pub struct Cr0Flags { > pub protection_enable: bool, >...

Thanks for this feature request. This is indeed flawed and I consider it to be a bug actually. A better codegen should help this.

That is a good idea, however, the problem is that `next` had some bugs that needed to be fixed. Also the work was only like 95% done. Bugs are a...