refactor: move task_fn into its own crate

tests/boundaries/deep_chains.rs

@@ -1,7 +1,7 @@
 //! Tests for extremely deep dependency chains
 
-use dagx::task_fn;
 use dagx::{DagResult, DagRunner};
+use dagx_test::task_fn;
 
 use std::sync::atomic::{AtomicUsize, Ordering};
 use std::sync::Arc;

tests/boundaries/type_limits.rs

@@ -1,7 +1,7 @@
 //! Tests for type system edge cases and limits
 
-use dagx::task_fn;
 use dagx::{DagResult, DagRunner, TaskHandle};
+use dagx_test::task_fn;
 
 use std::marker::PhantomData;
 

tests/boundaries/zero_tasks.rs

@@ -1,7 +1,7 @@
 //! Tests for empty DAGs and minimal task configurations
 
-use dagx::task_fn;
 use dagx::{task, DagResult, DagRunner};
+use dagx_test::task_fn;
 
 use tokio::task::yield_now;
 

tests/dependencies/resolution.rs

@@ -1,7 +1,7 @@
 //! Tests for dependency resolution order and transitive dependencies
 
-use dagx::task_fn;
 use dagx::{task, DagResult, DagRunner};
+use dagx_test::task_fn;
 
 use std::sync::{Arc, Mutex};
 

tests/dependencies/tuples.rs

@@ -1,7 +1,7 @@
 //! Tests for tuple dependencies (2-8 dependencies)
 
-use dagx::task_fn;
 use dagx::{DagResult, DagRunner};
+use dagx_test::task_fn;
 
 #[tokio::test]
 async fn test_two_dependencies() -> DagResult<()> {

tests/errors/propagation.rs

@@ -1,7 +1,7 @@
 //! Tests for error propagation through the DAG
 
-use dagx::task_fn;
 use dagx::{task, DagRunner, TaskHandle};
+use dagx_test::task_fn;
 
 use std::sync::Arc;
 use std::time::Duration;

tests/errors/recovery.rs

@@ -1,7 +1,7 @@
 //! Tests for error recovery patterns
 
-use dagx::task_fn;
 use dagx::{DagResult, DagRunner};
+use dagx_test::task_fn;
 
 use std::sync::atomic::{AtomicBool, AtomicUsize, Ordering};
 use std::sync::Arc;

tests/execution/mod.rs

@@ -1,5 +1,5 @@
 // Basic execution tests for DagRunner
-use dagx::task_fn;
+use dagx_test::task_fn;
 
 use dagx::*;
 

tests/parallelism/concurrent.rs

@@ -1,7 +1,7 @@
 //! Concurrent access tests
 
-use dagx::task_fn;
 use dagx::{task, DagRunner};
+use dagx_test::task_fn;
 
 use std::sync::atomic::{AtomicUsize, Ordering};
 use std::sync::Arc;

tests/parallelism/spawning.rs

@@ -1,7 +1,7 @@
 //! Tests for spawner functionality
 
-use dagx::task_fn;
 use dagx::{DagResult, DagRunner};
+use dagx_test::task_fn;
 
 use std::sync::atomic::{AtomicUsize, Ordering};
 use std::sync::Arc;

tests/parallelism/threads.rs

@@ -1,7 +1,7 @@
 //! Tests for multi-threading and concurrent execution
 
-use dagx::task_fn;
 use dagx::{task, DagResult, DagRunner, TaskHandle};
+use dagx_test::task_fn;
 
 use std::sync::atomic::{AtomicUsize, Ordering};
 use std::sync::Arc;

tests/parallelism/timing.rs

@@ -1,6 +1,7 @@
 //! Tests for timing and speedup verification
 
-use dagx::{task, task_fn, DagResult, DagRunner};
+use dagx::{task, DagResult, DagRunner};
+use dagx_test::task_fn;
 
 use std::{
     sync::{Arc, Mutex},

tests/runtimes/mod.rs

@@ -2,7 +2,8 @@
 
 use std::{any::Any, sync::Arc};
 
-use dagx::{task_fn, DagResult, DagRunner};
+use dagx::{DagResult, DagRunner};
+use dagx_test::task_fn;
 use futures_util::{future::BoxFuture, task::SpawnExt, Future};
 use test_case::test_case;
 

tests/timing/concurrent_access.rs

@@ -1,7 +1,7 @@
 //! Tests for concurrent access patterns and race conditions
 
-use dagx::task_fn;
 use dagx::{task, DagResult, DagRunner, TaskHandle};
+use dagx_test::task_fn;
 
 use std::sync::atomic::{AtomicBool, AtomicUsize, Ordering};
 use std::sync::Arc;

tests/timing/interleaving.rs

@@ -1,7 +1,7 @@
 //! Tests for forced execution interleaving patterns
 
-use dagx::task_fn;
 use dagx::{task, DagResult, DagRunner};
+use dagx_test::task_fn;
 
 use std::sync::atomic::{AtomicUsize, Ordering};
 use std::sync::Arc;