Benjamin Goldberg wrote:
In all cases that I can think of, your dynamic code is essentially a
string which gets eval()ed (with a language-dependent eval). The
solution is to make the eval() function/operator compile into a sequence
of operations along the lines of: Load the compiler for this language,
(if it’s not already loaded), pass that string to the compiler, run the
generated bytecode.
Seems like an awful lot of overhead for every keystroke, window event,
and async file operation.