fix: suppress future_not_send lint and tighten Send bounds

Add `#[allow(clippy::future_not_send)]` to chain invocation methods and
clarify Send requirements for `exec` bounds.

1 files changed, 9 insertions, 0 deletions

diff --git a/mingling_core/src/asset/core_invokes.rs b/mingling_core/src/asset/core_invokes.rs
index 07e5092..705568b 100644
--- a/mingling_core/src/asset/core_invokes.rs
+++ b/mingling_core/src/asset/core_invokes.rs
@@ -135,6 +135,9 @@ where
     ///
     /// It will not execute any program hooks, because this type is used for **bypassing** or **reusing**, not for flow control.
     #[might_be_async::func]
+    #[allow(clippy::future_not_send)]
+    // The generated future is only awaited within the single-threaded chain
+    // execution, so it does not need to be `Send`.
     pub fn invoke_once<C>(&self, value: T) -> ChainProcess<C>
     where
         C: ProgramCollect<Enum = C> + 'static,
@@ -165,6 +168,9 @@ where
     ///
     /// It will not execute any program hooks, because this type is used for **bypassing** or **reusing**, not for flow control.
     #[might_be_async::func]
+    // The generated future is only awaited within the single-threaded chain
+    // execution, so it does not need to be `Send`.
+    #[allow(clippy::future_not_send)]
     pub fn invoke_to_last<C>(&self, value: T) -> ChainProcess<C>
     where
         C: ProgramCollect<Enum = C> + 'static,
@@ -207,6 +213,9 @@ where
     ///
     /// It will not execute any program hooks, because this type is used for **bypassing** or **reusing**, not for flow control.
     #[might_be_async::func]
+    #[allow(clippy::future_not_send)]
+    // The generated future is only awaited within the single-threaded chain
+    // execution, so it does not need to be `Send`.
     pub fn invoke_to_result<C>(&self, value: T) -> RenderResult
     where
         C: ProgramCollect<Enum = C> + 'static,