bool, void, 그리고 comptime 타입

Beyond numbers, Zig has a handful of tiny primitives that show up everywhere: bool, void, and special compile-time number types. 🧩

A bool stores exactly one of two values: true or false. It drives every if statement and while condition you write.

Comparison operators produce booleans. The expression 5 > 3 evaluates to true, which you can store or test directly.

The void type represents the absence of a value. A function returning void hands back nothing meaningful when it finishes.

You see void as the return type of side-effect functions, and as the payload of containers that only care that a key exists.

An untyped whole number like 42 starts as a comptime_int. It has arbitrary precision and only gains a fixed width when assigned.

Similarly, an untyped decimal such as 3.14 is a comptime_float. It is exact at compile time before it becomes an f32 or f64.

Because they are compile-time only, these types can hold huge or tiny values precisely. They coerce into sized types when you use them.

In Zig a type is itself a value with the type named type. This is what lets functions accept and return types for generics.

The anyopaque type marks memory whose shape is unknown, often used at C boundaries where the layout is hidden from Zig.

Together these small types give Zig its foundation: booleans for logic, void for nothing, and comptime numbers for flexible literals.

You write the literal 100 with no type annotation. Before it is assigned anywhere, what type does Zig give it?

Remember the small primitives: bool for true or false, void for no value, and comptime_int and comptime_float for flexible literals. 🎯