Tür Çıkarımı ve Açık Türler

When you bind a value, Zig can figure out the type for you, or you can spell it out. Both rely on Zig's strong, static type system.

If the value makes the type obvious, let Zig infer it. const name = "Ada" is clearly text, so no annotation is needed.

To state a type yourself, write a colon and the type after the name. This is how you pin down an exact integer width.

An inferred integer literal becomes a comptime_int until you use it. When it lands in a slot, Zig coerces it to the needed width.

Sometimes the value alone is not enough. A var starting at 0 needs an explicit type so Zig knows whether it is a u8 or an i64.

A bare 3.14 is a comptime_float. Annotate it to choose f32 or f64 when precision and memory size actually matter to you.

When the type is obvious from context, dropping it keeps lines clean. Annotate only when it adds real clarity or is required.

Assign 5 to a u16 slot and the literal quietly fits. Zig performs safe coercion toward the declared type whenever it can.

At function signatures and data structures, types are always explicit. Inference is a local convenience, not a way to skip declarations.

Zig will not silently turn a float into an int for you. Mismatched types raise an error, keeping numeric behavior predictable.

Infer when the value speaks for itself; annotate when the type is the information a reader needs. Clarity should drive the choice.

You write var counter = 0; and Zig complains. Why does it want more from you?

You saw that Zig can infer a type from a clear value, or you can annotate one with a colon. Let clarity and required cases decide which to use. 🎯