A future for bitflags (opens in new tab)

I’ve been helping maintain the bitflags crate for a long time now. One of the first things I did when inheriting the library was release a 2.0 that tried to tighten up the internals a bit. The issue was mostly around how generated code behaved with #[derive]s. When you wrote: