How is this a JIT? Everything is compiled to machine code. There's no advanced type specialization or lazy deoptimization. It might as well be an in-memory, lazy, AOT compiler.
Yes... but it does that just-in-time, which is what JIT stands for.
> There's no advanced type specialization or lazy deoptimization.
I don't think those things are required for it to be a JIT are they? I'd say it's a static JIT, rather than a dynamic, profiling, and specialising JIT, but both are JITs.
> It might as well be an in-memory, lazy, AOT compiler.