We will eventually need to implement custom pointers for data allocated in oscars.
There are various questions that will need to answered surrounding this:
- What is the API for a custom pointer?
- What is the most optimal representation for that pointer?
- How should memory stores and loads work?
There's probably more questions, but we can add them to this issue as we go.
Ultimately, we need a stable way to refer to memory on the heap that can be at an arbitrary address. By having our own custom pointers, we ultimately buy some level of stability where we can "pin" a specific object or builtin to a location on the heap, which should hopefully allow us to serialize and deserialize the our heap regardless of arbitrary raw pointers to real memory.
We will eventually need to implement custom pointers for data allocated in oscars.
There are various questions that will need to answered surrounding this:
There's probably more questions, but we can add them to this issue as we go.
Ultimately, we need a stable way to refer to memory on the heap that can be at an arbitrary address. By having our own custom pointers, we ultimately buy some level of stability where we can "pin" a specific object or builtin to a location on the heap, which should hopefully allow us to serialize and deserialize the our heap regardless of arbitrary raw pointers to real memory.