Asupersync

Spec-first, cancel-correct, capability-secure async for Rust

cargo add asupersync --git https://github.com/Dicklesworthstone/asupersync

TL;DR

The Problem: Conventional executor APIs leave important lifecycle contracts to composition and discipline. Cancellation can abandon partial effects, detached tasks can outlive their owner, cleanup may be best-effort, and schedule dependent failures can be difficult to reproduce.

The Solution: Asupersync makes its core task-ownership and runtime-tracked effect contracts structural rather than conventional. Tasks are owned by regions that close to quiescence. Cancellation is an explicit request → drain → finalize protocol, with budgeted bounds on covered, cooperative paths; non-cooperative code and foreign calls do not acquire a universal shutdown bound. Runtime-managed effects require capabilities, with host-boundary exceptions documented explicitly. The lab runtime makes controlled schedules deterministic and replayable.

Why Asupersync?