Aura2026 Edition
Pre-stable

Stdlib, Modules & Imports

How modules, SDK injection, runtime and the standard-library surface fit into Aura today.

Aura’s standard-library and module story spans the compiler, aura-stdlib, aura-sdk, runtime crates and the top-level sdk/ distribution tree.

Imports

aura
import std::io
import aura::tensor

SDK installations can augment source with default standard modules based on imports. That behavior is part of SDK ergonomics, not a reason to hide module boundaries from the language model.

Runtime layers

The workspace separates:

  • aura-rt — runtime support,
  • aura-rt-native — native-oriented runtime support,
  • aura-stdlib — standard-library surface,
  • aura-sdk / sdk/ — developer-facing SDK content and docs.

Compatibility status

The stdlib is meaningful implementation, but Aura is still pre-stable. A future stable release should publish explicit compatibility guarantees for stdlib APIs separately from compiler package versioning.

Verification-aware collections work

Verifier-related modules include region/collection verification infrastructure. Public docs should distinguish those implementation modules from a claim that every stdlib operation is formally verified end-to-end.