I haven't liked how modules implemented in Metalua are not loadable in
the standard way via require [...] However, one could invoke Metalua from a custom searcher
stuffed in package.loaders.
I see :)
> Caveat: the metalua loader relies on LUA_MPATH / package.mpath
> instead of LUA_PATH / package.path
I'm a little bothered by the proliferation of path configuration (even
in standard Lua) just to make Lua find files in some local path. We
put path/?.so in LUA_CPATH and path/?.lua and path/?/init.lua in
LUA_PATH. Presumably we also now add path/?.luac and path/?/init.luac
to it as well. Then we append to LUA_MPATH for the .mlua files.