Stdlib module os.vitl
This page is a wiki-style reference for one concrete stdlib file. It explains what the file owns, where it fits in the family, and how to decide whether this is the right surface to depend on.
os.vitl.Family: stdlib
Kind: public stdlib surface
Page style: this reference follows the same “encyclopedic card + portrait + usage contract” logic as the keyword pages, but for stdlib modules.
Summary
Overview
| Field | Value |
|---|---|
| Path | os.vitl |
| Family | stdlib |
| Kind | public stdlib surface |
| Line count | 1001 |
| Declared procedures | 167 |
| Declared forms/picks | 30 |
`os.vitl` is a public stdlib surface inside the `stdlib` family. It should be read as one focused slice of the broader family responsibility: Top-level map of the Vitte standard library and the responsibilities owned by each family.
Purpose
This file should be chosen because of responsibility, not because its name “sounds close enough”. Inside the stdlib family, it carries one focused part of the contract and keeps that responsibility separate from neighboring concerns.
- 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`.
Top-level API inventory
| Surface | Items |
|---|---|
| Procedures | os_result_ok, os_result_error, os_error, errno_name, strerror, status_from_errno, getpid, getppid, getpgid, getsid, setpgid, fork |
| Forms | OsError, OsResult, Process, ProcessInfo, SpawnOptions, ExecResult, EnvVar, User, Group, SystemInfo, FileDescriptor, FileStat |
| Picks | OsStatus, PlatformKind, ProcessState, FileType, OpenMode, SignalDisposition |
| Constants | OS_VERSION, OK, ERR, EOF, EXIT_SUCCESS, EXIT_FAILURE, STDIN_FILENO, STDOUT_FILENO, STDERR_FILENO, SEEK_SET, SEEK_CUR, SEEK_END |
Imported surfaces
This file does not advertise a top-level `use` surface in its opening declarations. That often means it is either self-contained or an aggregation layer.
How to use this module
Start by reading the file as an ownership boundary. Ask three questions: what enters this module, what stable types or procedures it exports, and what adjacent module should stay outside of it.
- Open the family page first to understand why this area of the stdlib exists.
- Read the source excerpt below to see the namespace, imports, and first declared surfaces.
- Check the neighbor list to avoid coupling this module with an adjacent responsibility by habit.
Source shape
space vitte/stdlib_checked/os
const OS_VERSION: string = ""
const OK: int = 0
const ERR: int = 0
const EOF: int = 0
const EXIT_SUCCESS: int = 0
const EXIT_FAILURE: int = 0
const STDIN_FILENO: int = 0
const STDOUT_FILENO: int = 0
const STDERR_FILENO: int = 0The excerpt is not meant to replace the file. It exists to make the module recognizable at first glance, the same way a Wikipedia infobox helps the reader orient before reading the whole article.
Integration boundaries
Within stdlib, this file should remain focused. If a future helper changes the host boundary, scheduling boundary, or data-shape boundary, it probably belongs in a neighbor module instead of being added here by convenience.
- Family responsibility: Top-level map of the Vitte standard library and the responsibilities owned by each family.
- 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`.