Arwalk

Exceptions considered harmful

If you were to receive this code in review, would you accept it? typedef struct { const char* message; } FirstError; typedef struct { const char* message; } SecondError; static FirstError firstError = {0}; static SecondError secondError = {0}

Zig doesn't need X macros

If you remember the previous article C11 tying data to enums, you might know that I enjoy safety at compile time if I don’t have to compromise with exposing implementation to the

C11 : Tying data to enums

Let’s say you’re making a C library that deals with fruits.Fruits have many "attributes" that could be tied to them.They could have a size, a color, and a weight,