Results 144 comments of gingerBill

This probably needs to be disallowed.

Should be fixed in eac74631ecb74689dbe6bb1e1d07cd15f1fc677a.

`FOO {} //invalid syntax` Is actually valid syntax and semantics, it's just defining a `nil` procedure of `FOO` type However, this is a bug in the backend.

So we'd need to add something like the opposite of `@(init)` to the compiler since `os.args` is initialized before `main`.

This begs the question, is this something we should allow in the first place? `defer` really is an edge in many ways (e.g. it disallows `return` within it for loads...

The issue isn't `::` but rather procedure declarations with `defer` (I know what the bug is and how to fix it). I'm wondering what the best approach to this is....

Please use tabs for indentation to be consistent with the rest of the codebase. Otherwise looks fine.

I'm guessing I know exactly what is causing this: LLVM doesn't like large aggregate types.

What's interesting is that if you look at the generated IR, it does it correctly: ```llvm ; Function Attrs: nounwind define internal void @main.main(i8* noalias nocapture nonnull %__.context_ptr) #0 {...

The bug only occurs when using `-debug`. Therefore it is fundamentally a bug in LLVM that seems like it is not fixable by our side, even if use `runtime.memset` instead...