What I Learned Making My Own JIT Language

Re:What I Learned Making My Own JIT Language by naasking on Wednesday June 27, 2018 @02:25PM (#17410537)

It depends what you mean by "dynamic type". Since we're talking about some hypothetical dynamic language which is JIT-friendly, "dynamic type" could mean a "staged type" of some kind.

It's kind of like how some static languages use code generation, say, based on a database schema, which is then compiled, except this would happen at runtime. It would have to let you programmatically guide this process dynamically, but the result is very close in performance to a statically compiled language.

[ Parent | on HN ]

Re:What I Learned Making My Own JIT Language by kodablah on Wednesday June 27, 2018 @02:28PM (#17410577)

I mean it in the most traditional sense of the term, a type that nothing can be assumed about it until runtime (especially since GGP mentioned Ruby or Python, type hints notwithstanding). The more you can determine before execution, of course the more you can help your JIT/compiler and it becomes less dynamic. Code generation, macros, type providers, etc do not affect the language's type-dynamicness IMO.

[ Parent | on HN ]