Corbin Royer
Corbin Royer
Ohhhhh I see now. Well shoot. That is quite a handy little feature there. I quite like it haha. I can see how this would reduce overhead again because now...
@Qix- exactly. This is very clean. A lot easier than the way C++ does it, for sure! And I'll read up on the ABI you've written up!
@Qix- Possible methodologies for arrays could be like how Swift does them: ``` swift func foo([Int32] fish): Int {} ``` Incasing the type could be easier than parsing the variable...
I think all code should be global and can be globally referenced by default, however. I think you should be able to define local zones (e.g, only files in the...
Ah this is true. Well I guess you could use both... It could be defined as your zones make all the files in the scope of that zone "local", and...
I think in the end result... A language that doesn't enforce hierarchy will be the one that wins. Because now it's not placing any sort of file/module layout constraints on...
True, either way is good (won't matter to the compiler).
I think (as you said) custom operators but in a limited sense would be nice, being able to write arua in arua would help with reducing overhead.
Exactly. Because the thing with most languages, is they're written in itself.. Then some sort of C/C++ overhead for the compiler and the bootstraper. Which just takes up compiler time...
@Qix- Yes, I think that is perfectly reasonable. Due to the fact that if you allowed having these custom operators outside the module that defines the associative type, I would...