xdBronch
xdBronch
the stdlib already has [functions to print to a buffer](https://ziglang.org/documentation/master/std/#A;std:fmt.bufPrint) and with an arguably better API. im also a little confused about the other functions youve added, if i know...
I think the App + fields approach might be better since when you're initializing it you have to explicitly define all the fields, you can't accidentally leave something as `undefined`...
they could but i doubt that many people would, making users do something the safe and "correct" thing instead of the easy thing is kinda the zig way
that feels close to good. `app.* = .{...};` is a bit clunky and those simple init tuple function parameters are generally nice to use but passing functions seems odd to...
does this mean glfw and mach-glfw will be abandoned? or simply not one of mach-cores dependencies?
from discord convo maybe by default make it .Console on debug builds and .Windows on release builds? id imagine this is the behaviour most people would want but still let...
should be fixed now with the new autodocs system
`std.net.Address` uses `std.posix.sockaddr` which is the correct type as it will change depending on the platform but youre unconditionally using `std.os.linux`. heres the version that compiles ```zig const std =...
this isnt a bug, the iterator returns pointers to the keys and your keys are `*Foo` so each `foo` is a double pointer, `**Foo`. field access and the like only...
yea that message could definitely be improved