Thomas Schilling

Once we can call out to C, support for basic `IO` stuff should be straightforward.

Add support for `Double#` and its operations.

Right now, `CALL` has to check for partial application and overapplication. We should distinguish between a call of a known function (`CALL`) and a call of an unknown function (`APPLY`)....

The CALL instruction currently takes an arbitrary number of arguments and copies them into a new stack frame. We could adopt a Lua-style calling convention where switching to a new...

There's a lot of potential for off-by-one errors in the current code. In the interpreter R0 is at `base[0]`, but in the codegen it is at `[rbp + 8]`. A...

The bytecode compiler output format and the instruction set used by the interpreter should be separate. Reasons: - On 32 bit architectures a double needs two registers, on 64 bit...