Lurkie

@lunathemoongirl@cailincat.cloud I am generally a fan of the explicitness, but one area it can be annoying is with math. No operator overloading means geometric vector math is function/method calls. On the plus side, math is checked for overflow/underflow by default and zig has separate operators for wrapping and saturating arithmetic; I don't use them every day but it is quite handy when you do need them.

@lunathemoongirl@cailincat.cloud I'm a big fan of zig and have written quite a bit of code in it. Big changes are still happening in the standard library and language. The next major release (0.16.0) will introduce a new Io & async API, and the current release (0.15.2) introduced a streaming reader/writer api. I would say Zig feels like a modern version of C, with many of the jagged edges rounded off. Precision, verbosity, and explicitness are preferred over brevity and convenience.

@lunathemoongirl@cailincat.cloud yeah, compile time code execution (comptime for short) is used a lot in zig, for conditional compilation, generic data types, and type reflection. For example, the growable array in zig's standard library is a function that takes a type and returns a type. If you wanted a list of u8s, you would use std.ArrayList(u8). One of the quirky language features that enables this is lazy compilation. Zig won't analyze code unless it is actually used.