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.

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/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

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. Open the family page first to understand why this area of the stdlib exists.
2. Read the source excerpt below to see the namespace, imports, and first declared surfaces.
3. Check the neighbor list to avoid coupling this module with an adjacent responsibility by habit.

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.

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.

Neighbor modules

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