Hi,
On 2025-05-19 10:34, minung...@gmail.com wrote:
Hi,
Zig uses a WASM image to bootstrapt [1].
1. Use system C compiler to compile zig-wasm2.c
2. Use zig-wasm2.c to convert zig1.wasm.zst to zig1.c
3. Use system C compiler to compile zig1.c.
4. Use zig1 to build the Zig compiler into zig2.c
Hi,
Zig uses a WASM image to bootstrapt [1].
> 1. Use system C compiler to compile zig-wasm2.c
> 2. Use zig-wasm2.c to convert zig1.wasm.zst to zig1.c
> 3. Use system C compiler to compile zig1.c.
> 4. Use zig1 to build the Zig compiler into zig2.c
> 5. Use system C compiler to compile zig2.c
> 6
Hi,
On Tue, 13 May 2025 05:21:14 +0800
minung...@gmail.com wrote:
> But why Zig? As for me, Zig shows a possibitily to get rid of current
> toolchain. Even though C is not a bad language (I think C is good
> enough!), nowadays GCC is written in C++ which is a monster. Zig has
> lots of improvement
Hi,
> What actual concrete benefits would Zig have for the guix project,
> especially compared to guile?
Rewriting some components in zig is my long term target. My first target is
reducing the code base size and make it more modularity. I have done some
experiments on it [1][2]. Lots of code o
May 12, 2025 at 5:21 PM, minung...@gmail.com mailto:minung...@gmail.com wrote:
>
> Hello Guix,
>
> Today I successfully built guix-daemon using Zig build system [1]. This show
> the possibility of rewriting part of (or entire) gux-daemon in Zig. Zig can
> work as a C compiler. Although curr
