Miguel Ojeda

> There is no wishlist for what for rust conversion you would want in the C header file if you could have it. There is: https://github.com/Rust-for-Linux/linux/issues/353. (If you mean items...

Definitely, anything that can be automated is welcome. Especially things that contain a lot of repetition, like the one in the OP, are prime candidates. XML in comments would probably...

Perhaps it could skip those, but bindgen should not issue errors for valid C.

> The expectation is to have the frame_type macro definition. What do you mean by "macro definition"? A Rust macro? A `const fn`? i.e. please post the expected Rust code...

> Generating corresponding Rust code from C language macro definitions would be sufficient, whether as Rust functions or Rust macros. That would be very useful indeed (even if only for...

I think in general a tool that would automate some of these would be quite useful for some projects, e.g. in Linux we already had to rewrite ioctl macros (like...

I think I mention that above (i.e. `--blocklist-item MAX`) -- or do you mean something different? Thanks!

Ah, you mean the other one, i.e. if the `enum` has a name. (Edit: added above)

> Not breaking the build on new releases isn't really possible if you're denying warnings. Even with restricting the available lints to those available in a specific version, changes to...

Agreed, perfect stability is not required to make this useful. Getting rid of the majority of the cases already helps a lot on keeping a build warning-free as much as...