Rohlem
Rohlem
As documented in https://ziglang.org/documentation/master/#inline-fn, "arguments at an inline function callsite which are compile-time known are treated as [Compile Time Parameters](https://ziglang.org/documentation/master/#Compile-Time-Parameters)." `s0` is `comptime`-known in `test "bisect ok"`, however the variables...
> But is possible to provide some information to tell compiler to make code perform consistently? For your concrete example you can explicitly tell the compiler by adding an early...
As an additional idea, `zig release x.y.z` could edit the `build.zig.zon` file in the project root to hold `.version = x.y.z-dev` afterwards. And while at it, `zig release` could also...
It seems like this PR has had no outstanding issues for a while (over 2 months) now and keeps getting rebased/updated several times a week. First off, thank you @BratishkaErik...
@mlugg If I understand your comment correctly, the actual distinction here would be to mark the branches = code paths rather than the target block they lead to. I think...
> A while loop at codegen is two conditionals: 1) condition to enter the loop and 2) condition to keep going. For a loop to jump back up, 2) must...
>> Meanwhile, serious people will be 100% fine with the zig binary that does not depend on LLVM and Clang because they will have full access to these features via...
> preferring absolute paths If I understand correctly, these paths are baked into the binary. I would prefer if Zig artifacts had support for reproducibility (to the extent technically possible)....
@mnemnion From quick testing it seems like currently Zig strips only the path prefix of the root source file. So `zig test src/root.zig` would strip that file to `root.zig`, but...
> This doesn't work, unfortunately, because ./file.zig and ./src/file.zig can't be distinguished. @mnemnion Please re-read my message. The path prefix of the compilation's (EDIT:module's) root file is stripped from the...