2 ms·
I can't seem to find any information about this. What issues did LuaJIT maintainers have with upstream Lua?
by matheusmoreira 2y ago
I can't seem to find any information about this. What issues did LuaJIT maintainers have with upstream Lua?
- edflsafoiewq 2y agohttps://github.com/LuaJIT/LuaJIT/issues/929 https://github.com/LuaJIT/LuaJIT/issues/929
- matheusmoreira 2y ago> the real issues of the language > irrelevant or not-well-thought-out features Looking for specific examples of these. The scoped finalization construct cited in a sibling comments is a great example of this. Are there more?
- mardifoufs 2y agoThe issue linked in the sibling comment is the main one, but for a specific example of them having reservations about a feature in a more recent version, there's this: https://github.com/LuaJIT/LuaJIT/issues/1013#issuecomment-1606273526 https://github.com/LuaJIT/LuaJIT/issues/1013#issuecomment-16...
- matheusmoreira 2y agoThat's an awesome example, thank you. I'm making my own language and it's hard to overstate how thorny the evaluator and call stack code can get once seemingly neat features are added. I'll try to avoid making the same mistakes. I agree with him that implicit scopes for resource management serve no purpose in a dynamic language.
- bjconlan 2y agoOh wow, from Mike Pall himself (I know he "retired" from the maintainer position but glad he is still providing guidance (and then some id imagine)) Seeing a project and a community functioning like this is simply inspiring.