source: update struct layout enum usage

The enum member name case was changed in ziglang/zig@099f3c4039. This appears to be the only change required to bring us up to compatibility with zig 0.12.0-dev.3561+f45ba7d0c.
parser: produce helpful error messages on command line errors
2024-04-07 14:08:49 -07:00 · 2024-04-07 14:02:16 -07:00 · 2024-04-06 16:00:34 -07:00 · 2024-01-15 22:45:59 -08:00
4 changed files with 20 additions and 9 deletions
--- a/build.zig
+++ b/build.zig
@@ -1,11 +1,11 @@
 const std = @import("std");

 pub fn build(b: *std.Build) void {
-    const target: std.zig.CrossTarget = b.standardTargetOptions(.{});
+    const target: std.Build.ResolvedTarget = b.standardTargetOptions(.{});
    const optimize: std.builtin.Mode = b.standardOptimizeOption(.{});

    const noclip = b.addModule("noclip", .{
-        .source_file = .{ .path = "source/noclip.zig" },
+        .root_source_file = .{ .path = "source/noclip.zig" },
    });

    demo(b, noclip, target, optimize);
@@ -24,7 +24,7 @@ pub fn build(b: *std.Build) void {
 fn demo(
    b: *std.Build,
    noclip: *std.Build.Module,
-    target: std.zig.CrossTarget,
+    target: std.Build.ResolvedTarget,
    optimize: std.builtin.Mode,
 ) void {
    const demo_step = b.step("demo", "Build and install CLI demo program");
@@ -35,7 +35,7 @@ fn demo(
        .target = target,
        .optimize = optimize,
    });
-    exe.addModule("noclip", noclip);
+    exe.root_module.addImport("noclip", noclip);
    const install_demo = b.addInstallArtifact(exe, .{});

    demo_step.dependOn(&install_demo.step);
--- a/build.zig.zon
+++ b/build.zig.zon
@@ -0,0 +1,11 @@
+.{
+    .name = "NOCLIP",
+    .version = "0.1.0-pre",
+    .dependencies = .{},
+    .paths = .{
+        "source",
+        "build.zig",
+        "build.zig.zon",
+        "license",
+    },
+}
--- a/source/command.zig
+++ b/source/command.zig
@@ -446,21 +446,21 @@ pub fn CommandBuilder(comptime UserContext: type) type {
                }

                _ = @Type(.{ .Struct = .{
-                    .layout = .Auto,
+                    .layout = .auto,
                    .fields = tag_fields,
                    .decls = &.{},
                    .is_tuple = false,
                } });

                _ = @Type(.{ .Struct = .{
-                    .layout = .Auto,
+                    .layout = .auto,
                    .fields = env_var_fields,
                    .decls = &.{},
                    .is_tuple = false,
                } });

                return @Type(.{ .Struct = .{
-                    .layout = .Auto,
+                    .layout = .auto,
                    .fields = fields,
                    .decls = &.{},
                    .is_tuple = false,
@@ -519,7 +519,7 @@ pub fn CommandBuilder(comptime UserContext: type) type {
                }

                return @Type(.{ .Struct = .{
-                    .layout = .Auto,
+                    .layout = .auto,
                    .fields = fields,
                    .decls = &.{},
                    .is_tuple = false,
--- a/source/meta.zig
+++ b/source/meta.zig
@@ -265,7 +265,7 @@ pub const TupleBuilder = struct {
            }

            return @Type(.{ .Struct = .{
-                .layout = .Auto,
+                .layout = .auto,
                .fields = &fields,
                .decls = &.{},
                .is_tuple = true,
Author	SHA1	Message	Date
torque	d513aa4eaf	source: update struct layout enum usage The enum member name case was changed in ziglang/zig@099f3c4039. This appears to be the only change required to bring us up to compatibility with zig 0.12.0-dev.3561+f45ba7d0c.	2024-04-07 14:08:49 -07:00
torque	89360ac197	parser: produce helpful error messages on command line errors This is the first cut at providing human-readable context for command line parsing failures. Since these failures are due to incorrect input (normally produced by a human), closing the information loop at the human layer makes a hell of a lot more sense than dumping an error traceback with a (possibly cryptic) error name and calling it a day. This approach doesn't print anything out by default and still depends on the user to choose exactly how the handle and print the error message. Errors are propagated from subcommands, though they end up being copied, which shouldn't be strictly necessary. Maybe this can be improved in the future. OutOfMemory has been added to ParseError to simplify the code a bit. The demo has been updated with a simplistic example of what presenting error messages to the user may look like. I don't know that this produces useful messages for every possible failure scenario, but it does for the most common ones.	2024-04-07 14:02:16 -07:00
torque	a961b1930a	parser: run subcommand parsing/callbacks iteratively This changes the parse/callback flow so that subcommands are run iteratively from the base command rather than recursively. The primary advantages of this approach are some stack space savings and much less convoluted backtraces for deeply nested command hierarchies. The overall order of operations has not changed, i.e. the full command line is parsed before command callback dispatch starts. Fixes: #12	2024-04-06 16:00:34 -07:00
torque	074db7f4f6	build: update for zig-0.12.0-dev.2208+4debd4338 I may move this commit to a separate branch, since there are a variety of improvements that I think I want to get applied to the 0.11.x-compatible codebase still. However, I have also not been motivated to work on those fixes, since this codebase is kind of crusty due to being the first thing I ever wrote in zig. Doing a bigger rewrite might supply the motivation to make those improvements. I will have to think about it. For now, I am going to focus elsewhere.	2024-01-15 22:45:59 -08:00