#proc-macro #async #pub #conditional #extern #cfg-attr

macro qualifier_attr

Procedural macro attributes for adding "qualifiers" (pub, async, unsafe, const, extern "C", ...) to various items

10 releases

0.2.2 Aug 13, 2023
0.2.1 Aug 13, 2023
0.1.6 Apr 4, 2023
0.1.2 Mar 29, 2023

#199 in Rust patterns

Download history 27766/week @ 2024-07-22 29692/week @ 2024-07-29 48931/week @ 2024-08-05 31782/week @ 2024-08-12 28088/week @ 2024-08-19 29962/week @ 2024-08-26 26140/week @ 2024-09-02 23783/week @ 2024-09-09 134160/week @ 2024-09-16 71784/week @ 2024-09-23 398714/week @ 2024-09-30 696131/week @ 2024-10-07 568016/week @ 2024-10-14 144217/week @ 2024-10-21 37390/week @ 2024-10-28 31881/week @ 2024-11-04

916,715 downloads per month
Used in 787 crates (13 directly)

MIT/Apache

54KB
1.5K SLoC

qualifier_attr

Latest Version Downloads Documentation License Dependency Status

Procedural macro attributes for adding "qualifiers" to various items.

At the moment, the crate supports the following "qualifiers":

  • pub, pub(crate), etc. - visibility and restriction
  • default - default implementations (a feature of specialization)
  • async - asynchronous code, e.g. async fn
  • unsafe - unsafe code, e.g. unsafe fn, unsafe trait
  • const - code that may run at compile time, e.g. const fn
  • extern "ABI" - specifying an ABI, e.g. extern "C" fn

Limitations

  • It seems that rust-analyzer will sometimes complain when the attribute is used with modules.

Examples

#[macro_use]
extern crate qualifier_attr;

// We can add a qualifier to a function
// with an attribute.
#[qualifiers(const)]
fn const_fn() -> u32 {
    42
}

const CONST_RES: u32 = const_fn();

// It's not so impressive on its own,
// but with `cfg_attr`, it can be conditional.
#[cfg_attr(feature = "extern_c", no_mangle, qualifiers(pub, extern "C"))]
fn extern_c_fn() -> u32 {
    42
}

// It even works with types, imports, and more!
mod foo {
    #[qualifiers(pub)]
    struct Foo {
        x: i32,
        y: i32,
    }
}

#[qualifiers(pub)]
use foo::Foo;

// Traits and implementations too!?
#[cfg_attr(feature = "unsafe_quux", qualifiers(unsafe))]
trait Quux {
    fn quux_the_thing();
}

#[cfg_attr(feature = "unsafe_quux", qualifiers(unsafe))]
impl Quux for Foo {
    fn quux_the_thing() {
        println!("The thing was quuxed.");
    }
}

// You can add qualifiers to the fields of a
// struct as well with this special attribute.
#[field_qualifiers(x(pub), y(pub))]
struct Point2 {
    x: i32,
    y: i32,
}

#[field_qualifiers(_0(pub), _1(pub), _2(pub))]
struct Point3(i32, i32, i32);

Learn more about cfg_attr here.

Note on legacy attributes

Before version 0.2.0, this crate provided a separate attribute for each kind of item. While this should generally be a small win for compile times, it is generally not justified by the additional complexity. The legacy attributes are still available behind the default legacy_attrs feature flag, but their use is currently discouraged. In order to disable the legacy attributes, add the following to your Cargo.toml:

[dependencies]
qualifier_attr = { version = "0.2", default-features = false }

Similar crates

License

Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Dependencies

~240–690KB
~16K SLoC