3 ms·
Maybe also properly separated list/array, map/dict and set types? The I-am-everything-{} type in lua is a bit unergonomic when you want to use it as only such a
by zeotroph 8y ago
Maybe also properly separated list/array, map/dict and set types? The I-am-everything-{} type in lua is a bit unergonomic when you want to use it as only such a type and a stumbling block for unfamiliar users.
Can a project using 5.3 lua continue using existing .lua files but also write new files in .ljs?
> switch
Aren't match statements all the rage nowadays? Even C++20 get's one (with a silly name, of course)!
> class
Finally, setmetatable is nice, but, yes, "proper" not handrolled classes.
> const
Too few scripting languages have these. Do you intend to make this include interior mutability as well or is this only pointer deep?
- mingodad 8y agoThe general idea is to be able to reuse code as much as possible, and C/C++/Java/Javascript style syntax make a lot of code available and if we ditch the 1 based index in favor of 0 based it makes it even easier.
- mkl 8y agoIt looks like it's still 1-based currently, is that right? 1-based arrays have been the biggest obstacle to me using Lua.
- spc476 8y agoI did years of assembly, then C, and now Lua. I've yet to find the 1-based indexing to be an issue, and that's even having written a few C modules to manipulate Lua arrays. What is it about the 1-based arrays that is so off-putting?
- mingodad 8y agoAgain the point is easy code reuse.
- mingodad 8y agoYes you are right it's still 1 based to allow easy conversion from actual existing Lua projects.