Stdlib family stdlib
This family page is the encyclopedia entry for one stdlib area. It explains why the family exists, what responsibility belongs here, and which files make up the surface.
Overview
| Field | Value |
|---|---|
| Family | stdlib |
| Module count | 11 |
| Purpose | Top-level map of the Vitte standard library and the responsibilities owned by each family. |
Architecture role
A realistic Vitte program usually starts in `core`, grows through `collections` or `data`, crosses textual boundaries with `json` or `encoding`, touches the host with `path` or `io`, and only then reaches system-facing families like `kernel`, `ffi`, `async`, or `threading`.
Main responsibilities
- Give maintainers a stable mental model of the whole library surface.
- Separate pure transformations from host-facing and runtime-facing boundaries.
- Make it easy to explain where a new helper belongs before adding code.
Real usage story
- Domain values start in `core` and `strings`.
- Grouped data moves through `collections` or `data`.
- Structured export goes through `json` and `encoding`.
- Filesystem or process interaction goes through `path`, `io`, `os`, or `sysinfo`.
- Explicit runtime coordination goes through `async`, `threading`, `kernel`, or `ffi`.