Eliza Weisman
Eliza Weisman
Other compiler error message improvements: - consider making the `CompileResult` type's error component carry a list of error messages rather than a single one. - give AST nodes the ability...
See also #20
Also under consideration: consider making `state.eval()` return a `Result` or something rather than panicking; this way, error messages can be passed around and handled. Not sure if this would have...
Added unimplemented word: bd0b7e4a2f8de56e5a33c80999d18af6b3bfff53
Requires #17 and #15
Can this be solved by snarfing somebody else's standard lib source (i.e. Racket) and compiling it into Seax bytecode that can be linked in arbitrarily? That would be ideal, so...
I don't know very much about how a foreign-function interface works - this is an advanced topic we weren't able to cover in CMPSC420. Hopefully @janyljumadinova can offer some advice.
Here's some [documentation](http://doc.rust-lang.org/book/ffi.html) on C FFI in Rust. Might be helpful.
The potential issue with providing low-level core OS functionality through hooks into libc rather than through hand-rolled fake syscalls on the VM (which seems like the other option here) is...
Looks like this will be relatively difficult, as I believe it will require `unsafe` and messing around with raw pointers. I've set up a [new branch](https://github.com/hawkw/seax/tree/list-dev) to work on `List`...