Ashley Mannix

Thanks for pointing this out @mkroening. It looks like that bitfields library is already using proc macros, where adding attributes like this is more straightforward.

Hi @axelkar :wave: Thanks for the suggestion! This is something that would be out-of-scope for `bitflags` to support natively, since it doesn't just deal with flags where a single bit...

Hi @Caellian :wave: This is something you technically can do outside of the `bitflags` macro by defining your own newtype over `[T; N]` and implementing the `Bits` trait for it....

> Crate would probably require a whole separate codegen logic for arrays This is essentially the problem. The macros here are already complex, and since `macro_rules` macros don't have good...

Hi @petekubiak :wave: `defmt` is unfortunately a bit tricky to support in libraries, but we could look at adding support in [`bitflags_derive`](https://github.com/bitflags/bitflags-derive) for it.

Thanks for pointing that out @demhadais. That's certainly a point in favor of representing UUIDs as strings, but still isn't a single obviously correct representation for all possible users. I...

Ah yes, without `wasm-bindgen` being stable we’d need to add this behind a feature flag and using a compiler variable the same way we do for `zerocopy`. If you did...

Thanks for the suggestion @HaydenReeve! :+1: It definitely would be nice to be able to use expressions as columns.

I wonder if this is some variant of another macro lifetime related issue I noticed elsewhere recently. At some point it looks like the edition rules of the macro source...

Rust is already heavily used in production by many projects globally, and has been for a long time, so I don't think that's a strong motivation here. Aiming for a...