WASM models memory as a big array which is your heap, all memory management within that is up to you. There is no GC, there is no new / delete or anything else.

WASM models memory as a big array which is your heap, all memory management within that is up to you. There is no GC, there is no new / delete or anything else. For the use case of porting C programs to your web browser this is fine, for higher level languages you're a bit stuffed. I hope WASM gains some sort of GC eventually, because writing a GC in WASM will make me cry. :-(