On Wed, Sep 28, 2022 at 5:29 PM Wei Liu <wei.liu@xxxxxxxxxx> wrote: > > Just a general question: what is the house rule for adding new proc > macros? They are powerful tools. I can see their value in `module!` > because writing all that boilerplate by hand is just painful. Yet they > are not straightforward to understand. It is difficult, just by looking > at the macro, to fully grasp what the final code looks like (though the > rsi target will help). Is there a concern that proc macro gets abused? The rule is "use them as last resort". That is, they are not banned, but they need to be justified: if there is an alternative that is not too bad (e.g. in terms of ergonomics or implementation), then the alternative should be used instead. Nevertheless, sometimes they are very handy. Apart from `module!` here, we are currently using them in the full repo for vtables [1] and the Asahi M1 GPU driver is using them for versioning [2]. It is also possible to make proc macros easier to handle, for instance if we end up deciding to allow utilities like the `syn` crate. [1] https://github.com/Rust-for-Linux/linux/blob/fcad53ca9071c7bf6a412640a82e679bad6d1cd4/rust/macros/lib.rs#L99-L148 [2] https://github.com/AsahiLinux/linux/blob/3c8982e2c78c219bf96761445c8b73c2b3034fba/drivers/gpu/drm/asahi/fw/buffer.rs#L43-L56 Cheers, Miguel
