> "shared heap" I have a related idea in my mind for quite a while, in lieu of os level shared address space (which is not affordable to pity me 😔), I sketched it with mmap, thus such a "small, w/ self-contained-ptrs, shared heap" would need relocation for other processes to re-mmap it at possibly different start address, thus "relative pointers" feature (described in my post above) to mitigate/elide the relocation.
> zero-copy IPC Google protocol buffers already did this, but not intrinsic to the programming languages in use, I'd suggest that it'll be much much more pragmatic when the PL supports "relative pointers" and deref internal ptrs inside a data pack just like usual ptrs. It's dreamful to mmap a data file (or just some ram, in case it's some file under `/dev/shm/` as in Linux), and view its start address as a native ref/ptr to your native data structure / object, or container of them.
