Stdlib module tests/smoke.vit

Overview

`tests/smoke.vit` is a validation module inside the `tests` family. It should be read as one focused slice of the broader family responsibility: Stdlib-focused smoke and integration validation surfaces.

Purpose

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

• A smoke file should prove the library can still be loaded and exercised through its intended public paths.

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.
• Narrow dependency fan-in: a small set of imports suggests a focused collaboration surface.
• Validation-oriented module: expect example flows, smoke checks, or proof that other contracts remain stable.

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

• src/vitte/stdlib/core as core use src/vitte/stdlib/core/algorithms as core_algorithms use src/vitte/stdlib/core/concurrency as core_concurrency use src/vitte/stdlib/core/io_helpers as core_io_helpers use src/vitte/stdlib/core/memory as core_memory use src/vitte/stdlib/core/panic as core_panic use src/vitte/stdlib/core/types as core_types use src/vitte/stdlib/core/utils as core_utils use src/vitte/stdlib/io as io use src/vitte/stdlib/io/buffer as io_buffer use src/vitte/stdlib/io/file as io_file use src/vitte/stdlib/io/fileops as io_fileops use src/vitte/stdlib/io/stdio as io_stdio use src/vitte/stdlib/io/stream as io_stream use src/vitte/stdlib/compression as compression use src/vitte/stdlib/compression/algorithms as compression_algorithms use src/vitte/stdlib/compression/brotli as compression_brotli use src/vitte/stdlib/compression/deflate as compression_deflate use src/vitte/stdlib/compression/huffman as compression_huffman use src/vitte/stdlib/compression/interface as compression_interface use src/vitte/stdlib/compression/lz as compression_lz use src/vitte/stdlib/compression/stats as compression_stats use src/vitte/stdlib/async as async_root use src/vitte/stdlib/async/channel as async_channel use src/vitte/stdlib/async/executor as async_executor use src/vitte/stdlib/async/future as async_future use src/vitte/stdlib/crypto as crypto use src/vitte/stdlib/crypto/hash as crypto_hash use src/vitte/stdlib/crypto/hmac as crypto_hmac use src/vitte/stdlib/crypto/keyderivation as crypto_keyderivation use src/vitte/stdlib/crypto/random as crypto_random use src/vitte/stdlib/crypto/utils as crypto_utils use src/vitte/stdlib/json as json use src/vitte/stdlib/json/builder as json_builder use src/vitte/stdlib/json/parse as json_parse use src/vitte/stdlib/json/parser as json_parser use src/vitte/stdlib/json/schema as json_schema use src/vitte/stdlib/json/serialize as json_serialize use src/vitte/stdlib/json/stringify as json_stringify use src/vitte/stdlib/json/types as json_types use src/vitte/stdlib/path as path use src/vitte/stdlib/path/globbing as path_globbing use src/vitte/stdlib/path/manipulation as path_manipulation use src/vitte/stdlib/path/special as path_special use src/vitte/stdlib/path/walker as path_walker use src/vitte/stdlib/strings as strings use src/vitte/stdlib/regex as regex use src/vitte/stdlib/runtime as runtime use src/vitte/stdlib/sysinfo as sysinfo use src/vitte/stdlib/datetime as datetime use src/vitte/stdlib/os as os use src/vitte/stdlib/memory as memory use src/vitte/stdlib/math as math use src/vitte/stdlib/math/algebra as math_algebra use src/vitte/stdlib/math/arithmetic as math_arithmetic use src/vitte/stdlib/math/arrays as math_arrays use src/vitte/stdlib/math/calculus as math_calculus use src/vitte/stdlib/math/comparison as math_comparison use src/vitte/stdlib/math/complex as math_complex use src/vitte/stdlib/math/geometry as math_geometry use src/vitte/stdlib/math/logic as math_logic use src/vitte/stdlib/math/matrix as math_matrix use src/vitte/stdlib/math/modular as math_modular use src/vitte/stdlib/math/number_theory as math_number_theory use src/vitte/stdlib/math/powers as math_powers use src/vitte/stdlib/math/probability as math_probability use src/vitte/stdlib/math/roots as math_roots use src/vitte/stdlib/math/sequences as math_sequences use src/vitte/stdlib/math/sort as math_sort use src/vitte/stdlib/math/statistics as math_statistics use src/vitte/stdlib/math/topology as math_topology use src/vitte/stdlib/math/trigonometry as math_trigonometry use src/vitte/stdlib/math/vector as math_vector use src/vitte/stdlib/statistics/descriptive as statistics_descriptive use src/vitte/stdlib/statistics/distributions as statistics_distributions use src/vitte/stdlib/statistics/datasets as statistics_datasets use src/vitte/stdlib/statistics/hypothesis as statistics_hypothesis use src/vitte/stdlib/statistics/machine_learning as statistics_machine_learning use src/vitte/stdlib/statistics/preprocessing as statistics_preprocessing use src/vitte/stdlib/statistics/sampling as statistics_sampling use src/vitte/stdlib/statistics as statistics_root use src/vitte/stdlib/statistics/time_series as statistics_time_series use src/vitte/stdlib/statistics/utils as statistics_utils use src/vitte/stdlib/statistics/visualization as statistics_visualization proc stdlib_smoke_core

Position in family

This file is module 1 of 1 in the tests family when ordered by path. By procedure count it ranks 1, and by line count it ranks 1. 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 94 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 stdlib_smoke_core() -> bool { (line 96)
• proc stdlib_smoke_io() -> bool { (line 107)
• proc stdlib_smoke_compression() -> bool { (line 116)
• proc stdlib_smoke_async() -> bool { (line 127)
• proc stdlib_smoke_crypto() -> bool { (line 134)
• proc stdlib_smoke_json() -> bool { (line 143)
• proc stdlib_smoke_path() -> bool { (line 154)
• proc stdlib_smoke_system() -> bool { (line 162)
• proc stdlib_smoke_statistics() -> bool { (line 193)

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 tests/smoke.vit is explicit.
2. Traverse procedures in source order; the early helpers usually explain the naming and numeric conventions used later.
3. 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/tests_smoke
use vitte/stdlib_checked/tests_smoke
proc run_example() -> bool {
  let stdlib_smoke_core: bool = stdlib_smoke_core()
  let stdlib_smoke_io: bool = stdlib_smoke_io()
  let stdlib_smoke_compression: bool = stdlib_smoke_compression()
  let stdlib_smoke_async: bool = stdlib_smoke_async()
  let stdlib_smoke_crypto: bool = stdlib_smoke_crypto()
  let stdlib_smoke_json: bool = stdlib_smoke_json()
  let stdlib_smoke_path: bool = stdlib_smoke_path()
  let stdlib_smoke_system: bool = stdlib_smoke_system()
  let stdlib_smoke_statistics: bool = stdlib_smoke_statistics()
  let family_count: f64 = 9 as f64
  give stdlib_smoke_core and stdlib_smoke_io and stdlib_smoke_compression and stdlib_smoke_async and stdlib_smoke_crypto and stdlib_smoke_json and stdlib_smoke_path and stdlib_smoke_system and stdlib_smoke_statistics
}

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/stdlib_checked/tests_smoke
use src/vitte/stdlib/core as core
use src/vitte/stdlib/core/algorithms as core_algorithms
use src/vitte/stdlib/core/concurrency as core_concurrency
use src/vitte/stdlib/core/io_helpers as core_io_helpers
use src/vitte/stdlib/core/memory as core_memory
use src/vitte/stdlib/core/panic as core_panic
use src/vitte/stdlib/core/types as core_types
use src/vitte/stdlib/core/utils as core_utils
use src/vitte/stdlib/io as io

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.

• Line 1: space vitte/stdlib_checked/tests_smoke
• Line 3: use src/vitte/stdlib/core as core
• Line 4: use src/vitte/stdlib/core/algorithms as core_algorithms
• Line 5: use src/vitte/stdlib/core/concurrency as core_concurrency
• Line 6: use src/vitte/stdlib/core/io_helpers as core_io_helpers
• Line 7: use src/vitte/stdlib/core/memory as core_memory
• Line 8: use src/vitte/stdlib/core/panic as core_panic
• Line 9: use src/vitte/stdlib/core/types as core_types

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

Imports

Integration boundaries

Within tests, 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: Stdlib-focused smoke and integration validation surfaces.
• Family architecture role: This family exists to prove that the documented stdlib surfaces keep behaving as promised.

Composition guidance

Choose this module when

• Choose tests/smoke.vit when the main question is owned by this module rather than by transport, storage, orchestration, or user-interface code.
• A smoke file should prove the library can still be loaded and exercised through its intended public paths.

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 tests.
• Do not move production logic into this file just because the test already mentions it; keep proof and implementation separate.

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

• No close sibling module found in the same family bucket.