Frityet
Frityet
Currently compiles with `clang` and `gcc`
> Can you print buildenvs and provide full logs? > > ```lua > local buildenvs = import("package.tools.autoconf").buildenvs(package) > print(buildenvs) > ``` will do, is there a way to pipe that...
> > > Can you print buildenvs and provide full logs? > > > > ```lua > > > > local buildenvs = import("package.tools.autoconf").buildenvs(package) > > > > print(buildenvs) >...
> I think it's not too related to the Pegasus project, right? It is, sort of, you could either do the type documentation comments inline in the source (which then...
Maybe this shouldn't be an error on unknown pragma? I see the value of some pre-processing tools having custom pragmas
> Just to note that calls into C code cannot be JIT compiled, so if LuaLS calls into C a lot (into bee.lua), then it's likely the JIT isn't able...
> bee.lua uses the "classic Lua/C API". whoops i thought you meant using FFI >OTOH, I thought that simply switching to luajit runtime alone would have been enough to improve...
Are there any missing features compared to the vscode version?
Why is `LUAOT_MODULE_SOURCE_CODE` not precompiled with luac? It would fix the issue, unless theres a good reason its omitted. Im gonna try to see what precompiling would do...
Works great, slightly bigger binaries though (~10k?)