darling-0.3.3 has been yanked.
Darling
darling is a crate for proc macro authors, which enables parsing attributes into structs. It is heavily inspired by serde both in its internals and in its API.
Usage
darling provides a set of traits which can be derived or manually implemented.
FromMetaItemis used to extract values from a meta-item in an attribute. Implementations are likely reusable for many libraries, much likeFromStrorserde::Deserialize. Trait implementations are provided for primitives, some std types, and somesyntypes.FromDeriveInputis implemented or derived by each proc-macro crate which depends ondarling. This is the root for input parsing; it gets access to the identity, generics, and visibility of the target type, and can specify which attribute names should be parsed or forwarded from the input AST.FromFieldis implemented or derived by each proc-macro crate which depends ondarling. Structs deriving this trait will get access to the identity (if it exists), type, and visibility of the field.
Example
extern crate darling;
extern crate syn;
The above code will then be able to parse this input:
/// A doc comment which will be available in `MyTraitOpts::attrs`.
;
Features
Darling's features are built to work well for real-world projects.
- Defaults: Supports struct- and field-level defaults, using the same path syntax as
serde. - Field Renaming: Fields can have different names in usage vs. the backing code.
- Auto-populated fields: Structs deriving
FromDeriveInputandFromFieldcan declare properties namedident,vis,ty,attrs, andgenericsto automatically get copies of the matching values from the input AST.FromDeriveInputadditionally exposesdatato get access to the body of the deriving type, andFromVariantexposesfields. - Mapping function: Use
#[darling(map="path")]to specify a function that runs on the result of parsing a meta-item field. This can change the return type, which enables you to parse to an intermediate form and convert that to the type you need in your struct. - Skip fields: Use
#[darling(skip)]to mark a field that shouldn't be read from attribute meta-items. - Multiple-occurrence fields: Use
#[darling(multiple)]on aVecfield to allow that field to appear multiple times in the meta-item. Each occurrence will be pushed into theVec.