Add all the right typedefs.

At the moment, serialization takes and returns data using the MemoryInfo struct, which does the job but doesn't provide quite enough info. Perhaps have it take and return a space, one we get those working? The fact there's owning pointers being passed around doesn't help matters, either.

Write a main.cpp that can handle loading files and add it to the runtime.

Yay, no more generation of C++! Anyway, we need to write a new back-end which will be able to create the files our loading system can use.

At the moment we use if-else chains that have to handle all cases. Something more systematic would be nice.

An allocation space could be represented fairly well by a dedicated class. It would need functions for allocating an object, iterating over all objects, and deallocating the space. Maybe also something for object migration.

We need a list of Hisp source files and their expected output, together with a shell script to run and check for discrepancies.

At the moment, we assume any object can be allocated at any address. That's probably... not true.

At the moment, any kind of debugging or logging happens by calling free functions that print to standard error. Some kind of more systematic solution would be nice; in particular, being able to configure where the output is sent and what kind of data should be logged (and in what format!) would be nice.