Zig

Sooner or later we will need to add tests to check for regressions.

I propose the following three kinds of tests:

• Function unit tests (mainly for the parsing functions)
• I/O testing: simulate a client sending requests from a different process and check the responses are correct
• Internal state testing: simulate a client sending requests from a different process and check our intern

Replace usage of @bitcast with safer alternatives, it needs to work in debug builds

Currently when creating the FAT32 and MBR boot sectors, a stub x86 boot code is used to say that the image is non bootable.
The current x86 version (with the asm code) can be found in the kernel/arch/common.

There needs to be an ARM version.
All the code will need to do it print to the screen saying the image in not bootable and be a valid boot sector.

An __extension__ keyword not followed by any other tokens will crash, e.g. a file that just contains __extension__

thread 26702182 panic: index out of bounds
/Users/ehaas/source/arocc/src/Parser.zig:169:18: 0x108f30147 in Parser.eatToken (arocc)
    if (p.tok_ids[p.tok_i] == id) {
                 ^
/Users/ehaas/source/arocc/src/Parser.zig:595:22: 0x108f1abf8 in Parser.parse (arocc

I think it probably makes sense to automatically install the dependencies on a new project after creating it. It would remove a manual step in the quickstart guide.

It does require that npm be in the $PATH though, maybe that's a problem in some cases. Also there are folks that prefer yarn over npm?

@ttulka How would you feel about this?

Needing to load ROMs from the filesystem every time is really annoying. We can easily cache them in localStorage or something.

Also the load cart UI should be rethought to allow for "included ROMs", "saved ROMs", or "load from FOO"