unknown

Zig doesn't have an interface keyword, but supports interface-like abstractions through manual vtables—a pattern used extensively in the standard library for allocators, readers, and writers. An interface in Zig consists of a pointer to opaque data and a collection of function pointers (vtable), forming a fat pointer similar to Go's interface implementation. The article explains how to build vtable-based interfaces, why vtables are stored as pointers rather than embedded, and compares this approach to Go's built-in interfaces. It provides guidance on when to use interfaces (runtime polymorphism, library code, plugin systems) versus alternatives like generics, tagged unions, or concrete types, emphasizing Zig's philosophy of making abstraction costs explicit.

Interfaces in Zig

A place for Zig developers to share ideas, ask questions, and talk about all things Zig—whether you're building something new or just exploring the language.

<p>almost all modern language has interface, zig should have it too. people who do generic programming will suffer without interface.</p>
