2027 / Standard libraries

t.* namespace reference

Every library function a Trident program can call has a name under t., grouped by subject: t.text spells and parses text, t.math does arithmetic and geometry, and t.security signs, seals and compares secrets. Search by name or by what you want to do, then open an entry to read its parameters, result, faults and examples.

How to read an entry

Take t.text.of. It turns one value into its single canonical text spelling, so t.text.of(-42) returns "-42". Locale never changes the answer.

Its entry lists one parameter, value, the scalar to spell. The result is text. The faults say exactly what it refuses: an array, a chest or a null value fails with language, and anything past 16 MiB fails with input_limit. No result is published when it faults.

Trident

Calling it

A call names the full path. There is no import line.

i32 delta = -42
text shown = t.text.of(delta)   # "-42"

A library comes with a lend

Naming a function does not let a program call it. An application keeps a lend in _grant/grant.draft: the libraries it may use and their settings. The host compares the code with the lend in both directions. A launch stops if the code reaches a library the lend does not cover, or if the lend names a library no code uses.

Chest

A lend that admits one library

The report module writes log lines, so the lend names t.log and sets its threshold. Nothing else is lent.

u16 schemaVersion = 1
chest[] libraries = [
    {
        u16 schemaVersion = 1
        text id = "t.log"
        chest? config = {
            u16 schemaVersion = 1
            text threshold = "info"
        }
        chest[] storeSlots = []
    }
]

Each entry's library requirements list the provider and bounds the host must supply. The security reference shows how a grant is narrowed for a script.

Find a namespace or member

Loading the full reference…

Browse by subject

Choose a subject to list its functions and types.