Given that Neovim already bundles its own Lua interpreter, is there any incentive to keep the LuaJIT installation process in the build.lua? It seems to not affect behaviour in any meaningful way when I tried modifying the plugin and running without that specific step. It could cause luarocks to use some other lua version internally, but to my knowledge that does not change anything.
It's definitely the build step that takes the longest so eliminating it would be nice :)
If we're okay with the change I can make a pull request for it (or you could perform the change if you prefer).
Hey,
Given that Neovim already bundles its own Lua interpreter, is there any incentive to keep the LuaJIT installation process in the build.lua? It seems to not affect behaviour in any meaningful way when I tried modifying the plugin and running without that specific step. It could cause luarocks to use some other lua version internally, but to my knowledge that does not change anything.
It's definitely the build step that takes the longest so eliminating it would be nice :) If we're okay with the change I can make a pull request for it (or you could perform the change if you prefer).
Thanks!