Kevin Ramharak

Well I think the setup of `HIR`, `MIR` and `ASM` makes it very easy to transpile the program to a different source. It seems like you can add features and...

So i got sick of not being able to debug the `bf.ok` file correctly since my backend was only 'debuggable' when the virtual machine actually worked correctly. I decided to...

@adam-mcdaniel After some refactoring to make the code easier to debug I am happy to announce that the brainfuck interpreter works. Also on the note of x86 target I noticed...

The examples in `examples/copy_drop` print the same output as when running the executable generated by the C backend. Im working on implementing the C stdlib and writing the `ffi` functions...

Maybe im making this more complicated than needed. The problem im trying to solve is the following: I used to be able to write something like this ```rust #[doc("Finds the...

I made a similar suggestion in a different issue. Any ideas on how to implement this? And what the rules of such an interaction should be?

I'm not sure I understand. Would this require additional syntax in the Oak language? I think It should be somewhat abstract so that each backend can implement it. For example:...

Does this mean that every dereference of a pointer has to be checked? I'm assuming performance is not really a concern right now, but does this not generate a lot...

I would suggest to advise implementations to return a `#[extern]` directive? That should be enough for most implementations and keep the rust implementation clean.

An issue I am having with trying to seperate these is that the `panic()` feature currently writes output to 'stdout' on what goes wrong. Great for debugging but it depends...