5 ms·
Ravi: A dialect of Lua with optional static typing and JIT
- cassepipe 6y ago"My motivation is somewhat different - I want to enhance the VM to support more efficient operations when types are known. Type information can be exploited by JIT compilation technology to improve performance. At the same time, I want to keep the language safe and therefore usable by non-expert programmers." Seems very promising. I will try it.
- deleted 6y ago[deleted]
- anonymoushn 6y agoThis is a cool project, and I find the documentation quite useful. However, it is a tough sell to say that the JIT only works on the main stack, where almost none of my code is run.
- azhenley 6y agoAnyone know how it compares to Luau, which is also on the front page right now?
- anonymoushn 6y agoOne major difference is that you can download it, run it, and edit the source code.
- artemonster 6y agoAstrologers proclaim the week of Lua. Amount of Lua-related posts doubles!
- ravi-delia 6y agoI am...interested.
- as-j 6y agoRavi catches my interest, then frustrates me. The Lua 5.4* compatibility statement. “Well we’re 5.3, we forked 5.3 I don’t agree with a minor 5.4 detail so we’re stuck on 5.3” It’s similar to LuaJIT stuck on 5.1. I don’t think it does the Lua world any favors to be stuck on so many versions. It causes extra work for library developers, makes for poor code samples, and confusion for new adopters. It’s not like Lua is moving quickly with versions either. Every ~5 years for a minor version? *) yes I know 5.4 is brand new.
- anonymoushn 6y agoLua does not use semver. Every minor version is a breaking change like changing the way function environments work, adding integers and integer division, or adding <const> and <close>