Alloyed

Programmatic access?

2

So I'm developing an [LSP server](https://github.com/Microsoft/language-server-protocol) for lua. I'd like to include inline documentation, function signatures etc. Since my server and ldoc are both written in lua, It'd be nice...

More details in code review comments. These changes were necessary to get microprofile working using GCC on linux, with Vulkan timers enabled.

Calling os.exit() from within a test is not protected

1

To reproduce: ``` lua describe("tests", function() it("will exit early", function() os.exit(42) end) it("will never be run", function() print("here be dragons") end) end) ``` I was blindsided by this while integration...

There is no standard lua formatter

6

:thinking: I'm not willing to write my own but it's interesting that it doesn't exist to begin with prior art: https://github.com/trixnz/lua-fmt written by the vscode server author https://github.com/trixnz/vscode-lua

support Lua 5.4

5

Ideally, we should update our grammar to support the new features at the same time that we port to lua 5.4 as a runtime https://www.lua.org/versions.html

I just noticed the type sig of goto definition allows for multiple definition returns Use cases, if we have a method name without a type we should return a list...

external typing

1

Native modules can't be easily parsed the way lua can: for one we might not even have the source. So it makes sense to provide a .luacompleterc-inspired format that can...

completion/goto definition works pretty okay when you're pointing it at a plain expression/lhs. it doesn't understand the following examples, though: ```lua -- in comments "in strings" { at_table_lhs = {}}...

we can complete simple expressions, like ```lua module.a.b:c() ``` but only when we know the type of each of the ids. We should be equally informative in these kinds of...

mostly for windows users