Collections, Text, and Bytes
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.
Containers need context
Section titled “Containers need context”The Edition 1 tour uses an owned List<Int> and reads elements with .at(...). The complete example includes values supplied by modules and typed input. It is useful for reading composition, but is not an independently validated site example.
Text is not a byte count
Section titled “Text is not a byte count”The text-unit rules distinguish UTF-8 byte length, Unicode scalar count and grapheme segmentation. They also state that normalization is not implicit. Choose an operation by its declared unit; a visual character and a stored byte are not interchangeable indices.
Indexing is deliberately bounded
Section titled “Indexing is deliberately bounded”The 1.1.0 limitations retain a narrow legacy bracket form for a bound immutable array of four integers with a literal integer index. General dynamic bracket access, mutable brackets and slicing are not activated by that statement.
Do not infer general indexing support from an isolated successful array example. Consult the release’s exact container and access rules before adapting code, and keep compatibility limits attached to the result.