Stdlib module encoding/utf.vitl

Overview

`encoding/utf.vitl` is a public stdlib surface inside the `encoding` family. It should be read as one focused slice of the broader family responsibility: Text and byte encoding surfaces such as utf, base64, url, hex, html, legacy encodings, and unicode helpers.

Purpose

This file should be chosen because of responsibility, not because its name “sounds close enough”. Inside the encoding family, it carries one focused part of the contract and keeps that responsibility separate from neighboring concerns.

• A JSON payload can be rendered first, then base64-encoded for transport.
• A path or URL can be normalized before joining it with host-facing code.

Taxonomy

Think of this page as a generated encyclopedia entry rather than a hand-written tutorial. The goal is to show what kind of module this is, how dense it is, and what reading strategy makes sense before depending on it.

• Medium procedure surface: this file groups several related operations behind one namespace.
• Minimal top-level dependencies: the module reads as mostly self-contained from its opening declarations.
• Explicit export surface: the file ends with visible export declarations instead of relying only on implicit namespace discovery.

Implementation profile

This profile is inferred directly from the source text. It does not replace reading the file, but it tells you quickly whether the module is mostly declarative, loop-heavy, branch-heavy, or organized around many small exits.

Top-level API inventory

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.

Position in family

This file is module 8 of 9 in the encoding family when ordered by path. By procedure count it ranks 2, and by line count it ranks 4. Those ranks are useful as rough signals of breadth, not as quality judgments.

Declaration map

The declaration map turns raw source into a scan-friendly catalog. It is useful when the file is large enough that a reader wants to orient by kinds of surfaces first.

The table is exhaustive for top-level declarations of the selected kinds. This file declares 14 matching surfaces.

Representative signatures

These signatures are shown in source order so the page keeps the feel of a reference manual, not just a keyword cloud.

• proc utf8_encode(code_point: i32) -> string { (line 8)
• proc utf8_decode(encoded: string) -> i32 { (line 12)
• proc utf8_is_valid(text_value: string) -> int { (line 16)
• proc utf8_length(text_value: string) -> i32 { (line 20)
• proc utf8_byte_length(text_value: string) -> i32 { (line 24)
• proc utf8_char_at(text_value: string, index: i32) -> i32 { (line 28)
• proc utf8_substring(text_value: string, start: i32, end: i32) -> string { (line 32)
• proc utf16_encode(code_point: i32) -> string { (line 37)
• proc utf16_decode(encoded: string) -> i32 { (line 41)
• proc utf16_to_utf8(text_value: string) -> string { (line 45)
• proc utf8_to_utf16(text_value: string) -> string { (line 49)
• proc utf32_encode(code_point: i32) -> string { (line 54)
• proc utf32_decode(encoded: string) -> i32 { (line 58)

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.

1. Read space and top-level imports first so the ownership boundary of encoding/utf.vitl is explicit.
2. Traverse procedures in source order; the early helpers usually explain the naming and numeric conventions used later.
3. Use the source landmarks section below as a table of contents when the file is large.
4. Only after that compare neighbor modules, because the right boundary choice matters more than memorizing one helper name.

User example

This example is generated from the actual stdlib module surface. Its job is not to be the smallest snippet possible; its job is to show a realistic consumer-shaped file that exercises the module and mirrors the language keywords the module itself relies on.

space demo/encoding_utf
proc run_example() -> string {
    give "ok"
}
export run_example

Keyword coverage

This table makes the “all keywords of the module” requirement auditable. It compares the detected Vitte keywords in the source file with the generated consumer example above.

The generated snippet exercises every detected Vitte keyword used by this module.

Source shape

space vitte/encoding/utf
// UTF-8 encoding/decoding
proc utf8_encode(code_point: i32) -> string {
  give ""
}
proc utf8_decode(encoded: string) -> i32 {
  give 0
}
proc utf8_is_valid(text_value: string) -> int {
  give 0

The 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.

Source landmarks

Large files are easier to retain when they have visible landmarks. When the source contains explicit section banners, they are surfaced here; otherwise the first major declarations are used as anchors.

• UTF Encoding/Decoding Module

Source organization

When a file carries its own internal chaptering, those chapters usually reveal the intended reading order better than a flat symbol list. This section reconstructs that organization from the source itself.

Complete API catalog

This catalog is the exhaustive file-level index for the module. It is intentionally closer to a generated encyclopedia appendix than to a tutorial summary.

Procedures

Exports

Integration boundaries

Within encoding, 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: Text and byte encoding surfaces such as utf, base64, url, hex, html, legacy encodings, and unicode helpers.
• Family architecture role: Use `encoding` when values cross a textual or byte-oriented boundary and representation matters.

Composition guidance

Choose this module when

• Choose encoding/utf.vitl when the main question is owned by this module rather than by transport, storage, orchestration, or user-interface code.
• A JSON payload can be rendered first, then base64-encoded for transport.
• A path or URL can be normalized before joining it with host-facing code.

Pause before extending it when

• Avoid extending this file when the new helper mostly changes the boundary to host I/O, runtime coordination, or foreign integration instead of staying inside encoding.
• Check nearby modules such as encoding/base64.vitl, encoding/hex.vitl, encoding/html.vitl before adding convenience wrappers here.

Relationship table

This table keeps the page closer to a real encyclopedia entry: a module is easier to understand when compared with its nearest alternatives in the same family.

Neighbor modules

• encoding/base64.vitl
• encoding/hex.vitl
• encoding/html.vitl
• encoding/legacy.vitl
• encoding/unicode.vitl
• encoding/url.vitl
• encoding/utf8.vitl
• encoding.vitl