What's the most cursed Zig you can write?

Challenge
13

Not really cursed, more just unintuitive and non-obvious, but it was recently pointed out to me that there’s nothing stopping you from adding a main function to your build.zig and using it as the root source file for your executable:

const std = @import("std");

pub fn build(b: *std.Build) void {
    const target = b.standardTargetOptions(.{});
    const optimize = b.standardOptimizeOption(.{});

    const exe = b.addExecutable(.{
        .name = "foo",
        .root_module = b.createModule(.{
            .root_source_file = b.path("build.zig"),
            .target = target,
            .optimize = optimize,
        }),
    });

    b.installArtifact(exe);

    const run_exe = b.addRunArtifact(exe);
    run_exe.addArgs(b.args orelse &.{});
    run_exe.step.dependOn(b.getInstallStep());

    const run = b.step("run", "Run the app");
    run.dependOn(&run_exe.step);
}

pub fn main() void {
    std.debug.print("Hello, World!\n", .{});
}

This can actually be a useful way to organize code if you need to run small snippets of auxiliary Zig code (code generation, etc.) as part of your build but don’t want to put the code in its own source file.

18 Likes