I have a simple enum, that has a method to “convert” it to a colored string, but whenever I try to use it, I get an error “unable to resolve comptime value”, though this code is not intended to be ran on comptime, but even if zig is calculating all possible return values at comptime (since there is a very finite number of those) of this function:

I used to break down my large c/c++ projects with CMake and then add each part to main project using add_submodule command (the smaller parts were static or dynamic libraries). Also I used the same solution to use third-party libraries in my project.

I’m new to zig and learning it atm. So I tried to write my own unicode split function (because of reasons, please indulge me). Here it is:

I’m new to zig and learning it atm. When I use std.mem.splitAny or splitSequence or tokenize to split a console input string with a space as delimiter, it returns garbage. So I tried to write my own unicode split function. Here it is:

What is the syntax for having a for loop in zig with an increment?
In the code snippet below I wrote how it would look like in F#.
But how does it look like in zig?

I’ve been trying to create a system where i can store different types of data as “bundles”. The input order should not matter (i sort the input by their type), and i should be able to get only parts of the data.

While reading some of the standard library source code, I have encountered very little use of pointers for function parameters, even with const, unless that specific parameter is edited by the function. From my perspective, it doesn’t seem very efficient as you are making a complete copy of the argument (obviously a shallow copy). So why is this? Is it better than passing something as a constant pointer, or is it just the “idiomatic Zig way”?

By idiomatic, I am referring to the way a Zig programmer would expect them to work. I have the following matrix structure:

By idiomatic, I am referring to the way a zig programmer would expect them to work. I have the following matrix structure:

Please bear with this question as it might sound very dumb but this is my first experience with manual memory management.