Memory and services

Ordinary nC source has manual/raw memory semantics. Type checking does not add automatic release, ownership tracking or pointer-lifetime validation. The program must satisfy the material preconditions of each operation.

The spellings T*, p<T> and ptr<T> converge on typed pointer representations. Memory examples use operations such as rd, wr and off. Check allocation size, alignment, access type and address lifetime before dereferencing or computing an offset.

A pointer parameter does not implicitly carry allocation length. A function returning allocated storage does not arrange its eventual release. Read each memory API together with its examples and target provider.

The runtime supplies services such as output, files, strings and operating-system access. Availability depends on the compiler, provider and profile. Frontend recognition of a signature does not establish that its symbol can be resolved during linking.

Project modules use compact imports such as:

use <project:worker>;

Resolution must preserve unit identity and dependencies. Diagnose linkage failures through the project graph and a minimal reproduction. Objects and caches under .ncc are derived artifacts, not source files for publication.