Standard library and data formats¶
Arbor includes standard facilities for everyday programs and its own toolchain. This chapter describes their intended scope rather than a finalized module API.
Design documentation
This chapter describes the language design. Examples are illustrative; implementation availability and unresolved rules are explained in Design status.
Batteries are included: collections, numbers, modular arithmetic, Unicode strings, time, concurrency, logging, configuration, and testing all have standard support. Precise module names and the full v0.1 inventory remain to be planned.
JSON, TOML, and YAML are supported data formats. Full YAML is not required in
v0.1, but manifest.yaml must work through a documented supported subset.
Unsupported YAML constructs are rejected explicitly. The exact subset and
round-trip/serialization rules remain open.
The formatter, linter, documentation generator, and LSP are official tools, with machine-readable diagnostics and API information as a design goal. Formatting must not change string contents or program semantics.