ravi
ravi copied to clipboard
dibyendumajumdar
Ravi is a dialect of Lua, featuring limited optional static typing, JIT and AOT compilers
I would like to support running 5.1 scripts in Ravi, hence plan to add a compatibility layer for 5.1.
The [bitwise](https://github.com/dibyendumajumdar/ravi/blob/master/ravi-tests/bitwise_tests.lua) tests fail when compiled for 32-bit binary on Windows. The standard Lua tests complete successfully so the issue appears to occur when variables with type annotations are used.
Ravi already supports 64-bit integer along with double, or 32-bit integer along with float. I have not found a scenario where 64-bit integer is needed - so it would be...
Curious if you've made any progress on the `symbolic` extension mentioned in a talk you've given?
At present the JIT compilation blocks execution - this slows down overall execution; we need to perform JIT compilation in the background and let the execution continue in interpreted mode...
Lua bytecodes are well tested via the Lua testsuite; need to ensure that each Ravi bytecode also has a test case
The type of a logical operators and/or is determined based on the arguments - so this poses a problem when determining the return type statically. Possible solutions: We could specialise...
By doing escape analysis it should be possible to determine if a local variable can escape from a function. This would allow variables that are of primitive type to use...
When auto compiling all Lua functions, the memory usage increases greatly during the running of Lua tests. The problem has become apparent when running tests with -port=true; previously I was...
Metadata
Owner
Metadata
Ravi is a dialect of Lua, featuring limited optional static typing, JIT and AOT compilers