errors from Lua module interface are not developer friendly
I'm creating a "Hello world" Lua plugin and the process is not straightforward as I would wish.
Interestingly if a Lua module does not return a table (which is easy to forget when you start), it spits out quite confusing error message:
> modules.load('test') attempt to index a boolean value
I was looking into the C code which loads the Lua modules and it does not have any super-easy fix because of Lua-C integration. This lead me to idea that we might rewrite Lua-module loading into Lua, so it is not such a long spagetti. (Or not, if it does not simplify the code. I'm just thinking aloud.)