Message from JavaScript discussions

November 2018

— And also changes based on direct vs indirect eval call


The closure leak on the other hand, that will totally block gc until the whole context is terminated

— And it will block gc for the whole subsection of the stack inside

— Eval just delays gc, but the closure leak is a true memory leak

— Hz won't be able to transpile evals?

— I think it's a good limitation if it won't

— You can do it

— But why?

— Maybe the guy wanted to use eval for some reason

— Only at runtime

— Oof

— The call to it is intercepted as usual