Fix the #[macro_export] absolute path within the same crate issue

Author: danielhenrymantilla

pyo3-macros-backend/src/pyimpl.rs

@@ -266,7 +266,7 @@ fn add_shared_proto_slots(
             let first_implemented = implemented_proto_fragments.remove($first);
             let second_implemented = implemented_proto_fragments.remove($second);
             if first_implemented || second_implemented {
-                proto_impls.push(quote! { _pyo3::$slot!(#ty) })
+                proto_impls.push(quote! { _pyo3::class::impl_::$slot!(#ty) })
             }
         }};
     }

src/class/impl_.rs

@@ -183,6 +183,7 @@ macro_rules! define_pyclass_setattr_slot {
                 }
             }};
         }
+        pub use $generate_macro;
     };
 }
 
@@ -292,6 +293,7 @@ macro_rules! define_pyclass_binary_operator_slot {
                 }
             }};
         }
+        pub use $generate_macro;
     };
 }
 
@@ -484,6 +486,7 @@ macro_rules! generate_pyclass_pow_slot {
         }
     }};
 }
+pub use generate_pyclass_pow_slot;
 
 pub trait PyClassAllocImpl<T> {
     fn alloc_impl(self) -> Option<ffi::allocfunc>;