Research
What TCC does—and doesn't—claim.
TCC eliminates prefix replay when recovering from a committed continuation checkpoint.
It does not mean:
- Not O(1) recovery
- Not exactly-once external effects
- Not zero-overhead execution
- Not arbitrary TypeScript, Python, or Rust today
Continuation recovery alone cannot universally know whether an external API succeeded if the process dies after the side effect and before the completion record. Idempotency keys are part of the model; magical exactly-once I/O is not.
Language support is declared TypeScript, Python, and Rust subsets. Unsupported constructs fail at compile time rather than silently miscompile. More frontends are planned.