adam mcdaniel

Hmm, I hadn't considered how panic should be implemented. I think that panic info should be written to stdout for convenience sake, but I'm not really sure if there might...

Issue #68 has been fixed by PR #74, so now this might be something we could start working on. The main problem is that 99% of the typechecking errors are...

Example usage of the new additions to the standard library: ```rust #[std] struct Date { let m: num, d: num, y: num; fn now() -> Date { return [get_month_now() +...

Did you try placing the '-c' flag before the file argument? The `clap` crate might not parse the arguments in a different order without a special setting. I will look...

@kevinramharak I would probably implement it in Oak in `core.ok`, I think. This way its easier for us to hack at it

I think I would prefer to do something similar to Rust's take on variadic functions. I don't think functions _themselves_ should take a variable number of arguments, but I think...

I'm thinking something like this: ```rust #[std] #[macro print(arg, args[argc]) { if is_type(arg, num) { putnum(arg as num) } else if is_type(arg, &char) { putstr(arg as &char) } else if...

To do macros ***best***, I think we need to move away from having the parser spit out IR code. The parser should generate an AST node, which could then be...

Yes, TIR is a tree like structure, but it's a very strict structure. Information about the movability of objects and their members needs to be extracted here for use in...

All the AST would need to compute is 1. Computing every macro call until there are none left (There might need to be an iteration limit set by a flag...