Hi, Reading the thread it is likely that you are affected by LuaJIT issue#1167 . Unfortunately the interaction between the Lua and C semantics through the FFI is not trivial. You can try the proposed workarounds to force the JIT compiler analysis (or in general the VM) to see the object as used unti...

Thanks for the update. I found a repository with the MoonScript sources, but it doesn't have the amount of documentation I was hoping for, and maybe not the latest improvements too. Apparently there were desires to remove projects and contributions from the author, thus it's not as interesting to lo...

Hi, I'm interested in understanding/improving the performance issue, but it seems the repository has been removed. As a general solution to the JIT limitations I tend to use rudimentary dynamic compilation on top of it, i.e. to dynamically produce Lua code that can be more easily JIT compiled. But I...

Hi, I don't have the knowledge to easily and confidently build a shared library for Android, if that is even desirable. If you are already building LÖVE for the app, building WebP should probably be part of that process. Also, I am no longer working on that project; I archived it on GitHub. If I wor...

Now that LÖVE 11.4 is released and uses LuaJIT 2.1, this library should no longer be used. Here is the result with the built-in profiler with the same parameters by adding at the top of main.lua: require("jit.p").start("lv") 46% world.lua:193 <- 97% Garbage Collector <- 3% Compil...

Released 2.0.

Complete rework based on the xtype library, now a dependency.
It solves previous limitations, correctly handles inheritance and simplifies everything.

"Real" doesn't mean much. Lua coroutines are VM threads, and what are commonly called threads are system threads. Those mutexes are for VM threads, where there is concurrency, but not at the same level. E.g. think about a computer where there are system threads, but a single core, no instr...

Released version 1.1.

It features better error propagation and mutexes.

We can't just say that "Lua is slow by design" or "C is fast by design". There is a lot of work involved to make something fast, from the highest to lowest levels, from compiler developers to game developers. And being fast is not the only relevant thing; in fact, most of the cod...

I want to add something which seems to be lacking when speaking about optimizations and not the regular not subtle "you should not think about optimization". Optimizing is complicated. It's not just about the complexity of the optimization in itself, it's also about the heuristic behind it...