tokio-rs/tokio

The repository is a Cargo workspace organized around a public runtime crate and companion libraries. Applications enter through Rust APIs or generated main/test wrappers; scheduler and driver implementations remain internal. State lives primarily in memory, while filesystem and subprocess APIs cross into operating-system resources. CI and documentation hosting are separate operational surfaces.

• Cargo.toml defines five public crates and five internal workspace members, with crates.io patches redirecting companion dependencies to local source.
  Cargo.toml#L1-L23
• The tokio facade exposes feature-gated fs, process, runtime, signal, sync, task, and time modules; spawn is re-exported when rt is enabled.
  tokio/src/lib.rs#L564-L625
• Builder::build selects current-thread or multi-thread construction; Runtime::block_on enters runtime context before dispatching to that scheduler.
  tokio/src/runtime/builder.rs#L1144-L1151tokio/src/runtime/runtime.rs#L343-L382
• The multi-thread scheduler owns workers with transferable cores; its implementation explicitly describes work stealing and core handoff during block_in_place.
  tokio/src/runtime/scheduler/multi_thread/mod.rs#L49-L78tokio/src/runtime/scheduler/multi_thread/worker.rs#L1-L5
• Driver::new assembles I/O, signal, clock, and timer components; disabled I/O or timer access produces explicit enable_io/enable_time panic messages.
  tokio/src/runtime/driver.rs#L47-L65tokio/src/runtime/driver.rs#L91-L117
• The blocking pool handles non-async work, growing to a configured thread limit and queuing further requests; task::spawn_blocking delegates to runtime infrastructure.
  tokio/src/task/blocking.rs#L90-L104tokio/src/task/blocking.rs#L220-L225
• Companion boundaries separate stream adapters, feature-gated utility modules, procedural runtime wrappers, and testing helpers rather than embedding them all in tokio.
  tokio-stream/src/lib.rs#L76-L117tokio-util/src/lib.rs#L25-L65tokio-macros/src/entry.rs#L468-L519tokio-test/src/lib.rs#L12-L35
• CI defines nextest and doctest commands across Windows, Linux, and macOS; Netlify builds nightly API documentation into target/doc and redirects / to /tokio.
  .github/workflows/ci.yml#L94-L133netlify.toml#L1-L19