21 releases

0.10.3 Nov 17, 2024
0.10.1 Aug 27, 2024
0.9.2 Jun 22, 2024
0.9.1 Mar 23, 2024
0.2.2 Feb 12, 2022

#22 in Procedural macros

Download history 79210/week @ 2024-12-01 174454/week @ 2024-12-08 130572/week @ 2024-12-15 30966/week @ 2024-12-22 71668/week @ 2024-12-29 144662/week @ 2025-01-05 159536/week @ 2025-01-12 115592/week @ 2025-01-19 137904/week @ 2025-01-26 143552/week @ 2025-02-02 152945/week @ 2025-02-09 150251/week @ 2025-02-16 189533/week @ 2025-02-23 188832/week @ 2025-03-02 189758/week @ 2025-03-09 176480/week @ 2025-03-16

748,447 downloads per month
Used in 310 crates (21 directly)

MIT/Apache

67KB
1K SLoC

attribute-derive

docs.rs lib.rs MIT Documentation for main

Basically clap for attribute macros:

use attribute_derive::Attribute;
use syn::Type;

#[derive(Attribute)]
#[attribute(ident = collection)]
#[attribute(error(missing_field = "`{field}` was not specified"))]
struct CollectionAttribute {
    // Options are optional by default (will be set to None if not specified)
    authority: Option<String>,
    name: String,
    // Any type implementing default can be flagged as default
    // This will be set to Vec::default() when not specified
    #[attribute(optional)]
    views: Vec<Type>,
    // Booleans can be used without assigning a value, i.e., as a flag.
    // If omitted they are set to false
    some_flag: bool,
}

Will be able to parse an attribute like this:

#[collection(authority="Some String", name = r#"Another string"#, views = [Option, ()])]

Limitations

There are some limitations in syntax parsing that will be lifted future releases.

  • literals in top level (meaning something like #[attr(42, 3.14, "hi")]
  • function like arguments (something like #[attr(view(a = "test"))]
  • other syntaxes, maybe something like key: value

Parse methods

There are multiple ways of parsing a struct deriving Attribute.

For helper attributes there is:

For parsing a single TokenStream e.g. for parsing the proc macro input there a two ways:

Dependencies

~0.6–1MB
~22K SLoC