Christoffer Lerno
Christoffer Lerno
That's something that would require `@noinit`. Note that it would not be correct to elide the implicit zeroing in this case, since the bytes not affected by `snprintf` will not...
It would be an optimization, but none that the compiler can do without inlining the functions. If it did, then the zero init would be removed I'm sure. Unused local...
This is clearly a very rough idea. This is more intended for resource handling than memory management. Here would be a way to do `@pool` in a flat way: ```c...
However, this is not the only way to do "flat" `@pool`. We can also imagine macros that could insert defers, if so then we'd just do: ```c fn void test()...
The downside of macros that insert defers is that this hidden control flow can be hard to understand, even compared to lazy parameters, this s why `@defer` attributes might be...
It's not greatly prioritized, but it's one of those quality of life things – not having to open a scope unnecessarily. If we have `@defer(close)` as an attribute saying "store...
This might be desirable, but it's also surprising and very much special casing things.
I can't see how this could be fixed without special casing in a hard to describe way. Outside of eliminating C style const string concat.
@joshring raw strings also completely ignores escapes etc. So they're not the same thing. It's not a replacement. C string concat allows this: ```c String foo = "okeofkoekfe" "foekfeokfok" "ofekofkeokf";...
*Should* it cause an error?