You don't need that.
>>107891990Zig isn't memory safe, you shouldn't write software in Zig
Zig is an even bigger joke of a language than Jai, simply in terms of how its creator won't let it go anywhere.
>>107891990Python = PythonistasRust = RustaceansZig = ZiggersZiggers BTFO
>>107892070Rust = Rustranseans
>>107892003function foo allocate memory free memory write your code hereend fooHow is this not memory safe idiot
>>107891990are these retards unaware that you only need to write your own wrapper function a single time, and then you can reuse it forever?
>>107891990Zig has not reached version 1.0 yet. Do nocoders know what that means?
>>107892454You can allocate memory and free memory in the same place in zig, then do something with it and when it exits the scope it automatically drops it
>>107891990I don't get zig. It does the rust thing of making everything overly difficult to do. It does the c++ thing of being a dogshit language. But it also does the C thing of being riddled with memory errors? Who exactly is the audience for this language?>>107892542I as an experienced programmer happen to know it means you shouldn't touch the language with a ten foot pole. Hence why I wonder at all the people seemingly using the language.>>107892554You can "dude just remember to free when you allocate" in C. Do retards not understand why that isn't good enough?
>>107891990error: binary operator '&' has whitespace on one side, but not the other while (try std.io.Reader.takeDelimiterInclusive((*std.io.Reader) &reader, '\n')) |orig_line| {kek
error: binary operator '&' has whitespace on one side, but not the other while (try std.io.Reader.takeDelimiterInclusive((*std.io.Reader) &reader, '\n')) |orig_line| {
>>107891990Why do programmers always argue about stupid shit like this. Just write readfileintostring() if you want it and move the fuck on with your pathetic life
