Kairo Module and Import Declarations Reference

​

module

module <PascalCase.DotSeparated.Name>

• Exactly one module declaration per .ak file.
• Must be the first non-comment line.
• Segments use PascalCase; the full name uses dot separators.
• Multiple files may contribute to the same module.
• File paths are conventions only. The module declaration is authoritative.

module Astra.Customers.Models

​

import

import <Module.Name>

• Must appear after module and before declarations.
• No wildcard imports.
• Importing a module makes its public members accessible by name.

module Demo.App

import Astra.Data
import Pulse.Console

​

import ... as

import <Module.Name> as <Alias>

• The alias is file-local. It does not create a new module identity.
• Alias must be unique within the file’s import scope.
• Alias identifiers follow the same casing rule as the module segment they replace.

module Demo.App

import Astra.Net.Http as Http

​

import type

import type <Module.TypeName>

• Target must resolve to a type when metadata is available.
• Useful when the file only needs a specific type and not the whole module.
• Removes any ambiguity between module names and type names.

module Demo.App

import type Astra.Data.Database

​

Ordering and placement

​

Diagnostics

• Missing module declaration.
• module declaration not first in the file.
• Wildcard import used (not supported in v0.1).
• Alias already declared in this file.
• Type import target does not resolve to a type.

​

Related