feat: finish with clippy

Author: SRetip

module/core/derive_tools/Readme.md

@@ -1,4 +1,4 @@
-# Module :: derive_tools
+# Module :: `derive_tools`
 
 <!--{ generate.module_header{} }-->
 <!--{ generate.module_header.start() }-->

module/core/derive_tools/src/lib.rs

@@ -31,7 +31,7 @@
 // #[ cfg( feature = "enabled" ) ]
 // pub mod wtools;
 
-#[ cfg( all( feature = "derive_more" ) ) ]
+#[ cfg( feature = "derive_more" ) ]
 #[ allow( unused_imports ) ]
 mod derive_more
 {
@@ -110,6 +110,7 @@ pub use own::*;
 #[ allow( unused_imports ) ]
 pub mod own
 {
+  #[ allow( clippy::wildcard_imports ) ]
   use super::*;
   #[ doc( inline ) ]
   pub use orphan::*;
@@ -123,6 +124,7 @@ pub mod own
 #[ allow( unused_imports ) ]
 pub mod orphan
 {
+  #[ allow( clippy::wildcard_imports ) ]
   use super::*;
   #[ doc( inline ) ]
   pub use exposed::*;
@@ -133,11 +135,12 @@ pub mod orphan
 #[ allow( unused_imports ) ]
 pub mod exposed
 {
+  #[ allow( clippy::wildcard_imports ) ]
   use super::*;
   #[ doc( inline ) ]
   pub use prelude::*;
 
-  #[ cfg( all( feature = "derive_more" ) ) ]
+  #[ cfg( feature = "derive_more" ) ]
   #[ doc( inline ) ]
   pub use super::derive_more::*;
 

module/core/derive_tools_meta/Readme.md

@@ -1,5 +1,5 @@
 <!-- {{# generate.module_header{} #}} -->
-# Module :: derive_tools_meta
+# Module :: `derive_tools_meta`
 <!--{ generate.module_header.start() }-->
  [![experimental](https://raster.shields.io/static/v1?label=&message=experimental&color=orange)](https://github.com/emersion/stability-badges#experimental) [![rust-status](https://github.com/Wandalen/wTools/actions/workflows/module_derive_tools_meta_push.yml/badge.svg)](https://github.com/Wandalen/wTools/actions/workflows/module_derive_tools_meta_push.yml) [![docs.rs](https://img.shields.io/docsrs/derive_tools_meta?color=e3e8f0&logo=docs.rs)](https://docs.rs/derive_tools_meta) [![discord](https://img.shields.io/discord/872391416519737405?color=eee&logo=discord&logoColor=eee&label=ask)](https://discord.gg/m3YfbXpUUY)
 <!--{ generate.module_header.end }-->

module/core/derive_tools_meta/src/derive/as_ref.rs

@@ -1,4 +1,5 @@
 
+#[ allow( clippy::wildcard_imports ) ]
 use super::*;
 use macro_tools::{ attr, diag, item_struct, Result };
 

module/core/derive_tools_meta/src/derive/deref.rs

@@ -1,3 +1,4 @@
+#[ allow( clippy::wildcard_imports ) ]
 use super::*;
 use macro_tools::{ attr, diag, generic_params, Result, struct_like::StructLike };
 
@@ -11,7 +12,7 @@ pub fn deref( input : proc_macro::TokenStream ) -> Result< proc_macro2::TokenStr
   let item_name = &parsed.ident();
 
   let ( _generics_with_defaults, generics_impl, generics_ty, generics_where )
-  = generic_params::decompose( &parsed.generics() );
+  = generic_params::decompose( parsed.generics() );
 
   let result = match parsed
   {
@@ -84,6 +85,7 @@ pub fn deref( input : proc_macro::TokenStream ) -> Result< proc_macro2::TokenStr
 /// }
 /// ```
 ///
+#[ allow( clippy::unnecessary_wraps ) ]
 fn generate_unit
 (
   item_name : &syn::Ident,
@@ -322,9 +324,9 @@ fn generate_enum
     None => return generate_unit
     (
       item_name,
-      &generics_impl,
-      &generics_ty,
-      &generics_where,
+      generics_impl,
+      generics_ty,
+      generics_where,
     ),
   };
 
@@ -343,18 +345,18 @@ fn generate_enum
     generate_unit
     (
       item_name,
-      &generics_impl,
-      &generics_ty,
-      &generics_where,
+      generics_impl,
+      generics_ty,
+      generics_where,
     ),
 
     syn::Fields::Unnamed( ref item ) =>
     generate_enum_tuple_variants
     (
       item_name,
-      &generics_impl,
-      &generics_ty,
-      &generics_where,
+      generics_impl,
+      generics_ty,
+      generics_where,
       &idents,
       item,
     ),
@@ -363,9 +365,9 @@ fn generate_enum
     generate_enum_named_variants
     (
       item_name,
-      &generics_impl,
-      &generics_ty,
-      &generics_where,
+      generics_impl,
+      generics_ty,
+      generics_where,
       &idents,
       item,
     ),

module/core/derive_tools_meta/src/derive/from.rs

@@ -1,3 +1,4 @@
+#[ allow( clippy::wildcard_imports ) ]
 use super::*;
 use macro_tools::
 {
@@ -10,6 +11,7 @@ use macro_tools::
 };
 
 mod field_attributes;
+#[ allow( clippy::wildcard_imports ) ]
 use field_attributes::*;
 mod item_attributes;
 #[ allow( clippy::wildcard_imports ) ]
@@ -464,7 +466,7 @@ fn variant_generate
     return Ok( qt!{} )
   }
 
-  if fields.len() == 0
+  if fields.is_empty()
   {
     return Ok( qt!{} )
   }

module/core/derive_tools_meta/src/derive/from/field_attributes.rs

@@ -1,3 +1,4 @@
+#[ allow( clippy::wildcard_imports ) ]
 use super::*;
 use macro_tools::
 {
@@ -25,6 +26,7 @@ pub struct FieldAttributes
 impl FieldAttributes
 {
 
+  #[ allow( clippy::single_match ) ]
   pub fn from_attrs< 'a >( attrs : impl Iterator< Item = &'a syn::Attribute > ) -> Result< Self >
   {
     let mut result = Self::default();
@@ -50,7 +52,7 @@ impl FieldAttributes
     {
 
       let key_ident = attr.path().get_ident().ok_or_else( || error( attr ) )?;
-      let key_str = format!( "{}", key_ident );
+      let key_str = format!( "{key_ident}" );
 
       // attributes does not have to be known
       // if attr::is_standard( &key_str )
@@ -61,7 +63,7 @@ impl FieldAttributes
       match key_str.as_ref()
       {
         FieldAttributeConfig::KEYWORD => result.assign( FieldAttributeConfig::from_meta( attr )? ),
-        "debug" => {},
+        // "debug" => {},
         _ => {},
         // _ => return Err( error( attr ) ),
       }
@@ -95,17 +97,18 @@ impl AttributeComponent for FieldAttributeConfig
 {
   const KEYWORD : &'static str = "from";
 
+  #[ allow( clippy::match_wildcard_for_single_variants ) ]
   fn from_meta( attr : &syn::Attribute ) -> Result< Self >
   {
     match attr.meta
     {
       syn::Meta::List( ref meta_list ) =>
       {
-        return syn::parse2::< FieldAttributeConfig >( meta_list.tokens.clone() );
+        syn::parse2::< FieldAttributeConfig >( meta_list.tokens.clone() )
       },
       syn::Meta::Path( ref _path ) =>
       {
-        return Ok( Default::default() )
+        Ok( FieldAttributeConfig::default() )
       },
       _ => return_syn_err!( attr, "Expects an attribute of format `#[ from( on ) ]`. \nGot: {}", qt!{ #attr } ),
     }

module/core/derive_tools_meta/src/derive/from/item_attributes.rs

@@ -1,3 +1,4 @@
+#[ allow( clippy::wildcard_imports ) ]
 use super::*;
 use macro_tools::
 {
@@ -23,6 +24,7 @@ pub struct ItemAttributes
 impl ItemAttributes
 {
 
+  #[ allow( clippy::single_match ) ]
   pub fn from_attrs< 'a >( attrs : impl Iterator< Item = &'a syn::Attribute > ) -> Result< Self >
   {
     let mut result = Self::default();
@@ -48,7 +50,7 @@ impl ItemAttributes
     {
 
       let key_ident = attr.path().get_ident().ok_or_else( || error( attr ) )?;
-      let key_str = format!( "{}", key_ident );
+      let key_str = format!( "{key_ident}" );
 
       // attributes does not have to be known
       // if attr::is_standard( &key_str )
@@ -59,7 +61,7 @@ impl ItemAttributes
       match key_str.as_ref()
       {
         ItemAttributeConfig::KEYWORD => result.assign( ItemAttributeConfig::from_meta( attr )? ),
-        "debug" => {}
+        // "debug" => {}
         _ => {},
         // _ => return Err( error( attr ) ),
         // attributes does not have to be known
@@ -99,7 +101,7 @@ impl AttributeComponent for ItemAttributeConfig
     {
       syn::Meta::List( ref meta_list ) =>
       {
-        syn::parse2::< ItemAttributeConfig >( meta_list.tokens.clone() );
+        syn::parse2::< ItemAttributeConfig >( meta_list.tokens.clone() )
       },
       syn::Meta::Path( ref _path ) =>
       {

module/core/former/Readme.md

@@ -23,7 +23,7 @@ This approach abstracts away the need for manually implementing a builder for ea
 
 ## Comparison
 
-The Former crate and the abstract Builder pattern concept share a common goal: to construct complex objects step-by-step, ensuring they are always in a valid state and hiding internal structures. Both use a fluent interface for setting fields and support default values for fields that aren't explicitly set. They also have a finalization method to return the constructed object (.form() in Former, build() in [traditional Builder](https://refactoring.guru/design-patterns/builder)).
+The Former crate and the abstract Builder pattern concept share a common goal: to construct complex objects step-by-step, ensuring they are always in a valid state and hiding internal structures. Both use a fluent interface for setting fields and support default values for fields that aren't explicitly set. They also have a finalization method to return the constructed object (`.form()` in Former, `build()` in [traditional Builder](https://refactoring.guru/design-patterns/builder)).
 
 However, the Former crate extends the traditional Builder pattern by automating the generation of builder methods using macros. This eliminates the need for manual implementation, which is often required in the abstract concept. Additionally, Former supports nested builders and subformers for complex data structures, allowing for more sophisticated object construction.
 
@@ -660,7 +660,7 @@ Storage is not just a passive collection; it is an active part of a larger ecosy
 
 - **Former as an Active Manager**: The former is responsible for managing the storage, utilizing it to keep track of the object's evolving configuration. It orchestrates the formation process by handling intermediate states and preparing the object for its final form.
 - **Contextual Flexibility**: The context associated with the former adds an additional layer of flexibility, allowing the former to adjust its behavior based on the broader circumstances of the object's formation. This is particularly useful when the forming process involves conditions or states external to the object itself.
-- **FormingEnd Callback**: The `FormingEnd` callback is a dynamic component that defines the final steps of the forming process. It can modify the storage based on final adjustments, validate the object's readiness, or integrate the object into a larger structure, such as embedding it as a subformer within another structure.
+- **`FormingEnd` Callback**: The `FormingEnd` callback is a dynamic component that defines the final steps of the forming process. It can modify the storage based on final adjustments, validate the object's readiness, or integrate the object into a larger structure, such as embedding it as a subformer within another structure.
 
 These elements work in concert to ensure that the forming process is not only about building an object step-by-step but also about integrating it seamlessly into larger, more complex structures or systems.
 

module/core/former/src/lib.rs

@@ -22,6 +22,7 @@ pub use own::*;
 #[ allow( unused_imports ) ]
 pub mod own
 {
+  #[ allow( clippy::wildcard_imports ) ]
   use super::*;
   #[ doc( inline ) ]
   pub use orphan::*;
@@ -35,6 +36,7 @@ pub mod own
 #[ allow( unused_imports ) ]
 pub mod orphan
 {
+  #[ allow( clippy::wildcard_imports ) ]
   use super::*;
   #[ doc( inline ) ]
   pub use exposed::*;
@@ -45,6 +47,7 @@ pub mod orphan
 #[ allow( unused_imports ) ]
 pub mod exposed
 {
+  #[ allow( clippy::wildcard_imports ) ]
   use super::*;
 
   #[ doc( inline ) ]