Zig

https://github.com/ziglang/zig

Admin

General-purpose programming language and toolchain for maintaining robust, optimal, and reusable...

Tokens:32,373

Snippets:203

Trust Score:8

License:MIT

Update:1 week ago

Show doc for...

Tokens:

Raw

### Incremental Compilation File Naming

Source: https://github.com/ziglang/zig/blob/master/test/cases/README.md

For incremental compilation tests, create multiple files with a dot and an integer before the `.zig` extension. Each file can be a different kind of test (e.g., expecting compile errors or expecting to run and exit(0)). The test harness uses these files to simulate incremental compilation. At the time of writing, there is no way to specify multiple files being changed as part of an update.

```text
hello.0.zig
hello.1.zig
hello.2.zig
```

--------------------------------

### Limit Backends and Targets

Source: https://github.com/ziglang/zig/blob/master/test/cases/README.md

Place at the end of a Zig test file to limit which backends and targets are tested. The `// backend` comment specifies allowed backends (e.g., `selfhosted`, `llvm`), and `// target` specifies allowed targets (e.g., `x86_64-linux`, `x86_64-macos`). Possible backends include `auto` (default), `selfhosted` (equivalent to `-fno-llvm -fno-lld`), and `llvm` (equivalent to `-fllvm`).

```zig
// run
// backend=selfhosted,llvm
// target=x86_64-linux,x86_64-macos
```

Tokens:

Raw