Russel Winder

Just to note that whilst Debian is currently supporting 3.8, 3.9, 4.0, and 5.0, Fedora Rawhide only has 4.0, if you want something else, you have to build it yourself.

This and last released version sounds like a good plan. If people will not update their infrastructure then they should expect to use old versions of DStep.

The C code: ```c struct bitfield { unsigned int one : 4; unsigned int two : 8; unsigned int : 4; }; ``` which is an entirely valid, and compilable,...

On my x86_64 machine GCC always seems to compile bitfields to 32-bit, so I was wrong to put `ushort` in the D example, I think it should be uint for...

The padding is required because some memory mapped hardware control words have really weird structures with useful bits scattered through the word, and some bits unused. Rather than force people...

I added a couple of main functions to try and compare usage. So in C: ```c int main(const int argc, const char *const *const argv) { struct bitfield x =...

But the struct has only one member a, there should be no other members. If there is then D "bitfields" cannot do what C and C++ bitfields are for. The...

Understood that: bitfield x = {1, 2}; cannot be supported, but I also tried: bitfield x = bitfield(1, 2); which gave the same result. I am very close to constructing...

That all seems fine and reasonable, but what the bitfields mixin should do is disable the default initialiser and have one that initialises each field by using the appropriate bit...

I'll hack around it for now so I can do stuff, but as soon as a fix is available I'll ditch the hack.