Are we tracking any issues with Zig we want included in 0.12.0? I saw the zig roadmap video from Andrew and he's keen to include fixes for all the real world projects so people can pin to that version, and I didn't see roc mentioned. If we have anything significant we could add our issues to that milestone. The windows slow dynamic library thing comes to mind, not sure if there is anything else?
A message was moved here from #compiler development > decimal alignment by Luke Boswell.
for completeness, alignment of u128/i128 being 16 on x86
See also https://roc.zulipchat.com/#narrow/stream/395097-compiler-development/topic/Zig.20roadmap
https://ziglang.org/download/0.12.0/release-notes.html
Zig 0.12 just got released :tada:
Wow, big release. Also, I guess roc can now use a smaller version of zig that doesn't have llvm (though it is still early and we probably don't want it yet):
Zig now generates LLVM bitcode module files directly and then passes those to LLVM. This means that a Zig compiler built without LLVM libraries can still produce .bc files, which can then be passed to clang for compilation.
I like that split. Can generate bitcode, but doesn't actually have to depend on llvm at all
These were the builtin changes to upgrade from 0.11.0 to 0.12.0, thanks @Bryce Miller
I'm wondering if it's time we look at upgrading Roc to zig 12 now too?
I think zig 12 improves support for WASI and linking WASM modules so this will make the change to platform's owning building binaries easier.
Or maybe we jump straight to zig 0.13.0?
I guess we would want to upgrade LLVM though too.
@Folkert de Vries is upgrading LLVM painfree?
it's never entirely painfree but I have no reason to assume major issues. It looks like inkwell already supports 0.18 so that should not be a problem either
Last updated: Jul 06 2025 at 12:14 UTC