Save/Load interpreter state #30

being able to serialize interpreter state into an image and then deserialize and resume it later could be used for a lot of things:
moving workloads between physical servers, capturing snapshots for debugging, rollback-type lag compensation, maybe it could be useful for hibernating and forking (by deserializing same saved state multiple times) processes in a toy os.
My own use-case is to have player-programmable entities in videogames, and being able to save the game while they run and then load and have them continue execution as if nothing happened

I'd be up to try to implement this after async is implemented