You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(Echo): update architectural documentation and usage examples
- Align README.md crate references from `echo-scheduler` to `Echo` for consistency with internal naming
- Refine module structure documentation to reflect final synthesized architecture separation between generic `Queue` and application-specific `Scheduler`/`Task`
- Update code samples to match actual implementation patterns (e.g., `Builder::Create()` vs `New()`)
- Enhance Deep Dive explanations of work-stealing mechanics and context ownership model
- Clarify Mountain integration workflow showing `ActionEffect` execution through Echo's scheduler
These changes ensure documentation accuracy for the core concurrency system that drives Mountain's `ActionEffect` processing and Cocoon's extension host operations.
|**Performance**| Use lock-free data structures (`crossbeam-deque`) and a work-stealing algorithm to achieve maximum throughput and low-latency task execution. |`queue::StealingQueue`, `scheduler::Worker`|
66
-
|**Structured Concurrency**| Manage all asynchronous operations within a supervised pool of workers, providing graceful startup and shutdown, unlike fire-and-forget `tokio::spawn`. |`scheduler::Scheduler`, `SchedulerBuilder`|
67
-
|**Decoupling**| Separate the _submission_ of a task from its _execution_. The `AppRuntime` submits work, and the `Scheduler` handles how, when, and where it runs. |`Scheduler::Submit`, `task::Task`|
68
-
|**Resilience**| The scheduler's design is inherently resilient, as the failure of one task (if it panics) does not bring down the entire worker pool. |`scheduler::Worker` (execution loop) |
69
-
|**Composability**| Provide a simple, generic `Submit` API that accepts any `Future<Output = ()>`, making it easy to integrate with any asynchronous Rust code. |`task::Task`, `Scheduler::Submit`|
|**Performance**| Use lock-free data structures (`crossbeam-deque`) and a work-stealing algorithm to achieve maximum throughput and low-latency task execution. |`Queue::StealingQueue`, `Scheduler::Worker`|
65
+
|**Structured Concurrency**| Manage all asynchronous operations within a supervised pool of workers, providing graceful startup and shutdown, unlike fire-and-forget `tokio::spawn`. |`Scheduler::Scheduler`, `Scheduler::SchedulerBuilder`|
66
+
|**Decoupling**| Separate the _submission_ of a task from its _execution_. The application submits work, and the `Scheduler` handles how, when, and where it runs. |`Scheduler::Scheduler::Submit`, `Task::Task::Task`|
67
+
|**Resilience**| The scheduler's design is inherently resilient, as the failure of one task (if it panics) does not bring down the entire worker pool. |`Scheduler::Worker::Run` (execution loop)|
68
+
|**Composability**| Provide a simple, generic `Submit` API that accepts any `Future<Output = ()>`, making it easy to integrate with any asynchronous Rust code. |`Task::Task::Task`, `Scheduler::Scheduler::Submit`|
0 commit comments