Functions and Modules
Source boundary: This page summarizes the Edition 1 documentation shipped with
nebo-v1.1.0. It is a reading guide, not a fresh execution test or a compatibility guarantee for your compiler.
Receiver functions
Section titled “Receiver functions”The function production places a typed receiver before the function name, followed by parameters and a body. Its example uses a receiver and a typed argument, then returns an expression with .return. This is a guide to that published shape, not a complete calling-convention specification.
Module boundaries
Section titled “Module boundaries”The import and capsule rules describe explicit aliases, selective imports and reexports. A logical module identity is distinct from the filename used by a test harness. The rules also distinguish importing a pure interface from running an initializer.
The language tour supplies two companion source files and passes them as compilation units. Keep these inputs together when studying it; a main file copied without its providers is incomplete.
Limits
Section titled “Limits”Importing a module does not by itself grant filesystem, display or other environmental permissions. Do not assume an internal module or compiled interface is a stable public ABI. See CLI, runtime and ABI before using implementation-level contracts.