Matthew Lugg

Results 46 issues of Matthew Lugg

## How do I try it? **TL;DR:** `zig build --watch -fincremental --prominent-compile-errors`, either targeting `x86_64-linux` with the self-hosted backend, or just not emitting a binary (i.e. `-fno-emit-bin`). The easiest way...

incremental compilation

The Zig compiler currently fails to handle OOM correctly in many cases. Ideally, if semantic analysis OOMs, we would like to report an error message in `zcu.failed_analysis`. There are two...

enhancement

After ziglang/zig#21063 is merged, the Zig compiler is able to perform certain incremental updates correctly. There's still a ways to go before it's generally usable, but `-fno-emit-bin` builds will be...

enhancement

This PR resolves #23959 by first introducing a helpful compiler feature for debugging incremental compilation, and then using it to find the bug in that issue. A corresponding incremental test...

## Background After the merge of #22706 and #23919, you can now `@ptrCast` to a slice where the operand is *any* slice or single-item pointer. The idea, broadly speaking, is...

breaking
proposal
accepted

`std.Build.Step.Fmt` takes a `[]const []const u8` to represents its paths. They are interpreted as relative to the step's owner `Build`'s build root. This is inappropriate. They should likely be relative...

enhancement
breaking
standard library
zig build system

### Zig Version 0.15.0-dev.552+bc2f7c754 ### Steps to Reproduce and Observed Behavior * Create a `std.process.Child` with `.init` * Try to use its `stdout_behavior`/`stderr_behavior`/`stdin_behavior` to specify an existing `std.fs.File` as the...

enhancement
standard library

I unintentionally closed #23891 while pruning branches; this is the exact same diff. Resolves: #23869

Error values in Zig can be constructed in three ways: * `@errorFromInt`. This is just a low-level primitive which is useful in niche scenarios (usually ABI stuff, such as passing...

proposal