Zig build should error when overwriting output files

[wooster0]

const std = @import("std");

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

    const optimize = b.standardOptimizeOption(.{});

    const x = b.addExecutable(.{
        .name = "x",
        .root_source_file = b.path("x.zig"),
        .target = target,
        .optimize = optimize,
    });
    b.installArtifact(x);

    const y = b.addExecutable(.{
        .name = "x",
        .root_source_file = b.path("y.zig"),
        .target = target,
        .optimize = optimize,
    });
    b.installArtifact(y);
}

Can you spot the mistake? Indeed, I forgot to change the name of the second executable, which means it's going to output two different binaries at the same location in zig-out/bin/, silently causing only one binary to be outputted.

I propose to make the Zig build script error when this happens because I can't see a use case for ever wanting to overwrite a binary that you already installed. If you do so, you're more likely doing something wrong, no?
It should be possible to check for a file already existing of the same name before it outputs the file. This applies to anywhere Zig build can output files.

[rohlem]

It should be possible to check for a file already existing of the same name before it outputs the file.

Probably what you already meant, but this should of course be atomic.
So not checkExists -> createFile, but instead via a file creation flag that makes the operation fail if the file already exists.
(Or if the executable is already generated somewhere in the zig-cache first, a file copy with a flag that makes it fail if it would overwrite another file.)