Targets · Zig · Naming considerations
A Program name nests to any depth — Ui.Button.Integer.Increment . This page is how that dotted name is carried into Zig, which nests just as deeply.
How a Program becomes Zig, in parts. Start with the introduction, then follow each part into the rendered output and the runtime it links against.
Zig keeps the full path, lowercased to snake_case and joined with a dot — the same separator as Program.
In Zig a struct is also a namespace: a pub const can hold nested pub const structs and pub fn s, and files are structs too. So nesting a container inside a container is exactly idiomatic — nothing has to be faked. The only difference from Program is the snake_case convention on the segments.
Each namespace segment becomes a nested container ( pub const … = struct { … } , or an imported file of that name), and the leaf a pub fn inside it — so the path is a genuine, compiler-resolved member chain, every level real.
A record TYPE is a struct , a union TYPE a union(enum) ; a built-in value type folds to a native type ( Maths.Integer → i64 ).
Use nested struct containers. Zig keeps every level of the name real, with a real dot for the separator — the closest of all the targets to Program's own notation, alongside Swift and Rust (which uses :: ), and unlike Dart and Go , which must join with an underscore. The only identifiers ever rewritten are ordinary names that collide with a reserved word .