> It not compiled it JIT
It doesn't matter. Lobster performs full code analysis, statically. So it
doesn't matter how exactly it run, as JIT or Compile-to-C. As in both cases,
the infer and code analysis happens before.
My point was about type infer. The argument Nim has against the type infer
It not compiled it JIT ...
Implementation
> Choose between running directly using the convenient JIT, or compilation to
> C++ for extra speed.
As far as I understand, one reason Nim doesn't have powerful type inference
(like it can't infer backward) is compilation speed.
Lobster has very powerful type inference and its compile time, almost instant,
see [video about it](https://www.youtube.com/watch?v=uuPeBKdnBOI). When in Nim
even for
Weird coincidence, i found Lobster for the first time yesterday too. Spent a
few hours if anything that i like came out(not really no).
Just discovered Lobster. Ha, ha, all my proposals about Nim are basically about
turning Nim into Lobster.
