We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Split CRAFT from Homeblocks implemetation details.
Add CRAFT design
Add "Coroutines vs Callbacks" page Companion to the state-machine page: why the .thenValue -> co_await lift is more correct, not just prettier. Covers the surface-area reduction (O(call sites) -> O(awaitable impls)), the bug classes coroutines delete by construction (lifetime, type, exactly-once, error propagation, RAII across the await), and the ones they pointedly don't (shared-state, affinity). Grounded in vol_io_guard, sgs_keepalive, detach, and the ublk war story. Linked from Home + Sidebar.
Add "Coroutines as State Machines" page A standalone mental-model page: the two-state lowering of a co_await function into a heap frame + a resumable switch (continuation wiring, frame reload, reentry jump), then the same suspend/resume idea as a stackful folly::fibers task for contrast, and a side-by-side table. Wired into the sidebar and Home index. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add v8 coroutine migration page (Folly futures -> sisl::async) Wiki for engineers who know the old Folly-future architecture: how the HomeBlocks/HomeStore I/O path works on the C++23 sisl::async coroutine ("v8") stack, centered on the heap/allocation and threading/affinity differences, with annotated before/after of the hot write/read path. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>