SpireEnum
A Rust library that provides powerful macros for working with enums, designed to simplify delegation patterns and reduce boilerplate code when implementing traits and methods for enums.
Table of Contents
- Key Features
- Overview
- Alternatives
- Usage
- Example: Basic Usage
- Example: State Machine
- Troubleshooting
- Performance
- Contributing
Key Features:
- Automatic delegation: Automatically implement methods and traits for enums by delegating to their inner types.
- Flexibility: Provide case-by-case implementations when needed.
- Conversion utilities: Generate conversion methods between the enum and its variants.
- Reduce boilerplate: Eliminate repetitive match statements and error-prone manual delegation.
- Hygiene (IDE friendly!):
- Token spans are preserved.
- Macro only uses inputs feed into it, no reflection is performed, no files are read (no IO operations).
- No state is preserved between macro invocations, each invocation is completely isolated.
Overview
SpireEnum provides three macros that work together:
#[delegated_enum]- An attribute macro for defining enums with delegation capabilities.#[delegate_impl]- An attribute macro for implementing traits or methods for the enum.- (Generated on the fly)
delegate_[enum_name]- A declarative macro generated bydelegated_enum, one for each annotated enum.
Macros 1. and 2. work through several steps:
-
Parsing and Analysis: When you apply
#[delegated_enum]to an enum, the macro parses the enum definition, its settings and variants, analyzing the types and structures. -
Code Generation: Based on the analysis, the macro generates:
- A declarative macro (named
delegate_[enum_name]) that handles the delegation logic. [Optional]A new type for each variant.[Optional]Conversion (From<>,TryFrom<>) implementations between the enum and its variants.
- A declarative macro (named
-
Delegation Logic: The
#[delegate_impl]macro is applied on trait or inherent implementations of the enum, identifies delegation targets, then uses the generateddelegate_[enum_name]macro, expanding to the appropriate match statements that forward method calls to the inner types. -
The Generated Declarative Macro: The most interesting part is the generated declarative macro (e.g.,
delegate_my_enum!). This macro:- Takes trait implementations or methods as input
- Expands them into match statements that delegate to the appropriate variant's inner value
- Properly handles generic parameters, lifetimes, and other complex syntax elements.
Alternatives
- enum_delegate - The initial inspiration for this crate, I aimed to provide better features while avoiding that crate's drawbacks (the main ones being lack of hygiene, preserving state between macro invocations).
- delegation - A fork of
enum_delegate, which solves some of the old one's issues - though it takes a different approach compared tospire_enum. - enum_variant_type - Provides similar functionality to this crate's
generate_variantssetting.
Usage
1. #[delegated_enum] (Enum attribute macro)
This attribute is applied to an enum definition to enable delegation capabilities:
use delegated_enum;
The delegated_enum attribute supports several optional settings that control how the enum behaves:
1.1 Basic Usage
When used without any settings, delegated_enum generates:
- A declarative macro named
delegate_[enum_name]that can be used to implement delegated traits for the enum.
Which generates the declared enum, and this macro:
pub use delegate_media_content;
The macro may seem a bit cryptic, but it allows you to manually delegate impls in a very simple way:
// Let's Imagine that all variants of the enum `MediaContent` implement this trait:
// If you were to manually write that implementation for the enum, you would have to:
// That can obviously get very tedious if you're frequently using this pattern,
// that's where the generated macro (`delegate_media_content`) comes in:
Although it can be used manually, the generated declarative macro delegate_media_content is used by the #[delegate_impl] attribute macro in the
exact same way.
1.2 Conversion Settings
These are specified inside #[delegated_enum( **here** )], separated by commas.
1.2.1 impl_conversions
Enable automatic generation of conversion methods between the enum and its variants.
For each Variant:
TryFrom<Enum>forVariantFrom<Variant>forEnum
Which additionally generates:
// ... same for each other variant
These implementations facilitate conversions between the enums and its possible variants, especially when each variant has a unique type.
This setting is configurable in a per-variant basis, you may skip generating the implementations for certain variants by using the attribute # [dont_impl_conversions]:
1.2.2 impl_enum_try_into_variants
Similar to impl_conversions, except it only generates TryFrom<Enum> for each variant.
1.2.3 impl_variants_into_enum
Similar to impl_conversions, except it only generates From<Variant> for the enum.
1.3 Variant Types Generation
These are specified inside #[delegated_enum( **here** )], separated by commas.
1.3.1 generate_variants
Generates a new type for each variant:
Which additionally generates:
;
;
;
// And replaces the original enum's variant types with the generated ones:
Note that the declarative macro delegate_[enum_name] is also generated differently to handle the new variant types.
1.3.2 generate_variants( attrs = [attribute_list] )
Applies every attribute in [attribute_list] to each generated variant type.
Which will generate:
;
;
;
1.3.3 generate_variants( derive(trait_list) )
Shorthand for attrs = [derive(trait_list)]
Which will generate:
;
;
;
2. #[delegate_impl] (Inherent/Trait impl attribute macro)
This attribute should be applied to the enum's implementation blocks:
use delegate_impl;
Which generates:
Note that it uses the macro delegate_api_response, which would be generated by the enum annotated with #[delegated_enum].
2.1 Associated Types, Constants and Static Functions
Delegating these items is impossible since there's no enum value to match on, you must write that particular item manually if a trait requires these.
Example:
use ;
// Suppose you have this trait:
// And you wish to apply it to the enum:
// The only item that can be delegated is `fn apply(&self)`, other items must be manually written:
Note that you may still manually write the implementation of fn apply(&self), which will "override" what would be generated by the macro.
3. Variant Attributes
Attributes that can be applied on a per-variant basis.
3.1 #[dont_impl_conversions] / #[dont_generate_type] (Variant attributes)
3.2 #[delegate_via(|var| var.foo())] (Variant attribute)
When delegating methods, instead of calling the method directly on the variant, call the delegated method on the result of the closure inside
delegate_via.
Example:
This attribute affects how the macro delegate_[enum_name] will be generated, in this, changing it:
// From
// To
3.3 #[delegator] (Variant field attribute)
Use this to delegate method calls to a field of the variant instead of the variant itself.
Example:
This will change the Legacy case in the delegate_[enum_name] macro:
// From
Config::Legacy { version: $arg, .. } => { $($Rest)* }
// To
Config::Legacy { config: $arg, .. } => { $($Rest)* }
Example: Basic Usage
use ;
let some_variant: Value =..;
println!;
Example: State Machine
SpireEnum is particularly useful for implementing state machines:
// Each state already has its own variant type declared outside the macro, no need to use `generate_variants`.
// Common interface for all states
// Implementation delegated to each state.
Troubleshooting
The macros provided by this crate carefully parse the inputs provided to it, I aimed to provide helpful error messages as reasonably as I could. If you encounter a cryptic error message, please open an issue, I'll do what I can to fix it.
1. "Cannot find macro delegate_[enum_name]"
You're likely using the macro #[delegate_impl] outside of the module that contains your enum.
The macro delegate_[enum_name] is generated alongside the enum annotated with #[delegated_enum],
you need to import it on other modules where #[delegate_impl] is used:
use ;
Performance
The delegation macros generate code that is equivalent to what you would write manually with match statements. There is no runtime overhead compared to manually written code.
Contributing
The best way to contribute is by using the crate and providing feedback. Please open an issue if you'd like to request a feature or report a bug.