A Zig package that provides a complete and lightweight wrapper around the Lua C API. Ziglua currently supports the latest releases of Lua 5.1, 5.2, 5.3, and 5.4 and targets Zig master. Tagged versions of Ziglua are made for stable Zig releases.

Ziglua can be used in two ways, either

• embedded to statically embed the Lua VM in a Zig program,
• or as a shared module to create Lua libraries that can be loaded at runtime in other Lua-based software.

In both cases, Ziglua will compile Lua from source and link against your Zig code making it easy to create software that integrates with Lua without requiring any system Lua libraries.

Like the Lua C API, the Ziglua API "emphasizes flexibility and simplicity... common tasks may involve several API calls. This may be boring, but it gives us full control over all the details" (Programming In Lua 4th Edition). However, Ziglua takes advantage of Zig's features to make it easier and safer to interact with the Lua API.

Docs are a work in progress and are automatically generated for each push to main. Most functions and public declarations are documented.

• Ziglua for Lua 5.1 Docs
• Ziglua for Lua 5.2 Docs
• Ziglua for Lua 5.3 Docs
• Ziglua for Lua 5.4 Docs

See docs.md for more general information on Ziglua and how it differs from the C API.

Example code is included in the examples directory.

• Run an example with zig build run-example-<name>
• Install an example with zig build install-example-<name>

In a nutshell, Ziglua is a simple wrapper around the C API you would get by using Zig's @cImport(). Ziglua aims to mirror the Lua C API as closely as possible, while improving ergonomics using Zig's features. For example:

• Zig error unions to require failure state handling
• Null-terminated slices instead of C strings
• Type-checked enums for parameters and return values
• Compiler-enforced checking of optional pointers
• Better types in many cases (e.g. bool instead of int)

While there are some helper functions added to complement the C API, Ziglua aims to remain low-level. This allows full access to the Lua API through a layer of Zig's improvements over C.

First create a build.zig.zon file in your Zig project if you do not already have one. Add a ziglua dependency.

.{
    .name = "myproject",
    .version = "0.0.1",
    .dependencies = .{
        .ziglua = .{
            // Use a tagged release of Ziglua tracking a stable Zig release
            .url = "https://github.com/natecraddock/ziglua/archive/refs/tags/0.2.0.tar.gz",

            // Or a url with a hash for a specific Ziglua commit
            .url = "https://github.com/natecraddock/ziglua/archive/ab111adb06d2d4dc187ee9e1e352617ca8659155.tar.gz",
        },
    }
}

When you run zig build it will instruct you to add a .hash field to this file.

In your build.zig file create and use the dependency

pub fn build(b: *std.Build) void {
    // ... snip ...

    const ziglua = b.dependency("ziglua", .{
        .target = target,
        .optimize = optimize,
    });

    // ... snip ...

    // add the ziglua module and lua artifact
    exe.addModule("ziglua", ziglua.module("ziglua"));
    exe.linkLibrary(ziglua.artifact("lua"));

}

This will compile the Lua C sources and link with your project. The ziglua module will now be available in your code. Here is a simple example that pushes and inspects an integer on the Lua stack:

const std = @import("std");
const ziglua = @import("ziglua");

const Lua = ziglua.Lua;

pub fn main() anyerror!void {
    // Create an allocator
    var gpa = std.heap.GeneralPurposeAllocator(.{}){};
    const allocator = gpa.allocator();
    defer _ = gpa.deinit();

    // Initialize the Lua vm
    var lua = try Lua.init(allocator);
    defer lua.deinit();

    // Add an integer to the Lua stack and retrieve it
    lua.pushInteger(42);
    std.debug.print("{}\n", .{try lua.toInteger(1)});
}

Please make suggestions, report bugs, and create pull requests. Anyone is welcome to contribute!

I only use a subset of the Lua API through Ziglua, so if there are parts that aren't easy to use or understand, please fix it yourself or let me know!

Thanks to the following sources:

• zoltan for insights into compiling Lua with Zig
• zig-autolua for help on writing an alloc function
• mach-glfw for inspiration on a clean build.zig

And finally Lua. Thank you to the Lua team for creating such a great language!