16.5 Runtime-backed surfaces
Some corelib APIs are thin wrappers over runtime builtins; know the boundary before you blame the language.
Runtime-backed surfaces
Not every stdlib function is a pure Beskid algorithm you can read over coffee. Some surfaces are runtime-backed: fibers, channels, syscall bridges, and other contracts where getting it wrong means blaming the runtime team in all caps.
How to tell
Section titled “How to tell”- Platform-spec marks runtime-backed areas explicitly—start at Runtime-backed corelib surfaces.
- Implementation lives split between
beskid_corelibpackages andpackages/runtime/beskid_runtime—the book is not a substitute for the crate map in chapter 13.
Stability
Section titled “Stability”Corelib API shape tiers are normative under Stability and API shape. Shipping breaking changes without a spec delta is how you lose friends at code review.