In einem Schritt kompilieren und ausführen

Normally you compile code into a binary, then run it. Zig folds both into a single friendly command: zig run. ⚡

Point zig run at a source file and it compiles your program and immediately executes the result, all in one go.

For a single file you need no build script and no project setup. That makes zig run perfect for quick experiments and learning.

Behind the scenes Zig still compiles to native machine code first. You simply never have to name or launch the binary yourself.

The executable from zig run is placed in a cache and run for you. It is not dropped into your folder as a permanent file.

Put two dashes after the file name, then your program's own arguments follow. Zig hands everything after -- to your code.

Add an optimize flag to control speed and safety. The default is the safe Debug mode, which keeps checks turned on.

Zig caches compiled artifacts, so running the same unchanged file again skips most work and starts almost instantly.

To keep a binary you can ship, use zig build-exe instead. It writes an executable to disk rather than running it for you.

During development you live in a tight edit-run loop. zig run keeps that loop fast: change the file, run it, see output, repeat.

If your code will not compile, zig run prints the errors and never runs anything. A clean compile is required before execution.

You have one file, app.zig, and want to compile and execute it in a single command. Which do you use?

Use zig run to compile and execute a file in one step, great for fast iteration. Reach for zig build-exe when you need a binary to keep. 🎯