refactor!: Rewrote device implementation macro once again
This time with a bit more though put into the design of the code, as a result the macro should be a lot more robust. This did result in the macro getting renamed from LuaDevice to Device as this should be _the_ Device macro. The attribute also got renamed from traits() to device(traits()) and the syntax got overhauled to allow for a bit more expression.
This commit is contained in:
@@ -1,13 +1,12 @@
|
||||
#![feature(iter_intersperse)]
|
||||
mod impl_device;
|
||||
#![feature(iterator_try_collect)]
|
||||
mod device;
|
||||
mod lua_device_config;
|
||||
|
||||
use lua_device_config::impl_lua_device_config_macro;
|
||||
use quote::quote;
|
||||
use syn::{DeriveInput, parse_macro_input};
|
||||
|
||||
use crate::impl_device::impl_device_macro;
|
||||
|
||||
#[proc_macro_derive(LuaDeviceConfig, attributes(device_config))]
|
||||
pub fn lua_device_config_derive(input: proc_macro::TokenStream) -> proc_macro::TokenStream {
|
||||
let ast = parse_macro_input!(input as DeriveInput);
|
||||
@@ -15,13 +14,6 @@ pub fn lua_device_config_derive(input: proc_macro::TokenStream) -> proc_macro::T
|
||||
impl_lua_device_config_macro(&ast).into()
|
||||
}
|
||||
|
||||
#[proc_macro_derive(LuaDevice, attributes(traits))]
|
||||
pub fn impl_device(input: proc_macro::TokenStream) -> proc_macro::TokenStream {
|
||||
let ast = parse_macro_input!(input as DeriveInput);
|
||||
|
||||
impl_device_macro(&ast).into()
|
||||
}
|
||||
|
||||
#[proc_macro_derive(LuaSerialize, attributes(traits))]
|
||||
pub fn lua_serialize(input: proc_macro::TokenStream) -> proc_macro::TokenStream {
|
||||
let ast = parse_macro_input!(input as DeriveInput);
|
||||
@@ -37,3 +29,31 @@ pub fn lua_serialize(input: proc_macro::TokenStream) -> proc_macro::TokenStream
|
||||
}
|
||||
.into()
|
||||
}
|
||||
|
||||
/// Derive macro generating an impl for the trait `::mlua::UserData`
|
||||
///
|
||||
/// The `device(traits)` attribute can be used to tell the macro what traits are implemented so that
|
||||
/// the appropriate methods can automatically be registered.
|
||||
/// If the struct does not have any type parameters the syntax is very simple:
|
||||
/// ```
|
||||
/// #[device(traits(TraitA, TraitB))]
|
||||
/// ```
|
||||
///
|
||||
/// If the type does have type parameters you will have to manually specify all variations that
|
||||
/// have the trait available:
|
||||
/// ```
|
||||
/// #[device(traits(TraitA, TraitB for <StateA>, <StateB>))]
|
||||
/// ```
|
||||
/// If multiple of these attributes are specified they will all combined appropriately.
|
||||
///
|
||||
///
|
||||
/// # NOTE
|
||||
/// If your type _has_ type parameters any instance of the traits attribute that does not specify
|
||||
/// any type parameters will have the traits applied to _all_ other type parameter variations
|
||||
/// listed in the other trait attributes. This behavior only applies if there is at least one
|
||||
/// instance with type parameters specified.
|
||||
#[proc_macro_derive(Device, attributes(device))]
|
||||
pub fn device(input: proc_macro::TokenStream) -> proc_macro::TokenStream {
|
||||
let ast = parse_macro_input!(input as DeriveInput);
|
||||
device::device(&ast).into()
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user