Hisham Muhammad

@GECORegulatory A major problem with recommending downstream packages first in the upstream documentation is that those packages are often out-of-date. The Ubuntu packages for LuaRocks have been a major version...

My knowledge about Windows is minimal, so your expertise is very welcome! I have a few questions about the design choices for handling this: - if we detect the OS...

> For LuaRocks I think it is ok assume that target os is os where it installed. If this is already what is happening with MSVC, then it would be...

Yes, the design is intentional. The documentation is unfortunately lacking (and help would be much appreciated!) but here is a summary from the original design document: https://github.com/luarocks/luarocks/wiki/Project:-LuaRocks-per-project-workflow

Note for beginners wanting to take on this issue: one way to add this is to make the Lua version exposed in a `LUA_VERSION` variable in a similar way that...

> Bug or User Error ? The latest code in `master` includes better diagnostic messages to make it clearer which case it is! Apart from that, it's what @Tieske and...

> Backward compatibility issues aside We cannot brush backward compatibility aside. :) > I think a scriptable package typically has its own mechanism to decide where to look for libraries....

> This is not true (in LuaRocks 3 at least). Note that my example uses luacheck installed straight from LuaRocks. Ahh, missed that, you're right — in that case it's...

@ator-dev `arg` as a function's vararg was deprecated back in 2006, see section 7.1: https://www.lua.org/manual/5.1/manual.html. The idiom for that since Lua 5.1, which Teal also adopts, is `{...}`. (Lua 5.1...

> I remember scouring the Teal documentation (and eventually the issues) trying to find an answer; maybe there's a relevant docs section where this could be noted? We don't really...