Kevin Ramharak

Well, I think most runtimes have some form of error reporting. That would be a great start. I think requiring it to exit with an error code fairly standard. Having...

Well, as far as I know we have to capture from which tokens the AST nodes are created and then pass them down correctly. The `@L` and `@R` in lalrpop...

I like this idea. Would `Range` be an internal type or would you actually implement it in oak?

Hm, im not familiar with how rust macro's work but that sounds pretty cool. Also makes it easier to do the variadic stuff at compile time as the runtime wont...

This seems like a good start. I think it would be a great replacement to having to write out all the `put*` functions right now.

I am a bit confused on what the difference between the AST and the current TIR would be. Are they not already a tree like structure?

Right, an AST with interchangable nodes would make optimizing easier. The attempt in PR #77 is very limited in that regard.

It should be improved to be more generic as its a bit fixated at certain rules at the moment. But this should make it easier to write `.ok` programs for...

I'm starting to get familiar with the code base. Any ideas on how to structure the documentation? Would be a good idea to set up some sort of skeleton so...

Those flags would be great features to add. The extern flag would be a great addition. Conditional compiling would also be really useful. I am a bit confused on the...