Run elisp on deno with deno's GC/Allocation about emacs-ng HOT 1 OPEN

Thinking this over, specifically handing over allocation to the v8 GC, one of the issues I am having is that the rusty_v8 doesn't have great bindings for finalizer callbacks, and as far as I can tell, FinalizationRegistry is broken in Deno due to their implementation of microtasks. I could give a deep dive into Deno to fix up FinalizationRegistry, but I am hesitant on that.

Luckily for us, WeakRefs work. The main issue is that once a proxy is GC'd, we need some way to know about that in order to call free on its associated proxy'd memory (read its internal field). We can do this purely with WeakRefs and a timer (have a native array of allocations, and an array of WeakRefs. Perform a comparison between the two and free everything not in the WeakRef array), however that is honestly kind of hacky to me, and takes away from the power of the v8 GC.

I think there are a lot of benefits to the lisp -> js compiler, however before we switch allocation to purely v8, the first thing we would need to work out is the finalization callbacks. Unfortunately for us, Deno does not using the proxying technique very much, so some of these code paths have issues.

from emacs-ng.