Alex Orlenko

I’m afraid they cannot. Blanket implementation is already taken by `T where T: UserData`

It definitely should be possible, but not yet in plans for the 1.0 release. Personaly I don't use Rust nostd support.

The reason why I skipped `&Lua` from interrupt callback arguments is because of unclear status of interrupts. Not all operations are permitted inside callback. But there is no list of...

Thanks for the PR! I was thinking about it and probably will prefer a bit more flixible approach by having `AsChunk` implemented for `Path`. I see it requires some changes...

From the [`doc`](https://docs.rs/mlua/latest/mlua/struct.Lua.html#method.unsafe_new) you need to use `Lua::new_unsafe` to load DLLs

Could you provide a code example? `__gc` is reserved for internal use (for `Drop` especially) but you should be able to do cleanup by implementing `drop()`. If you want in...

Probably the easiest option would be passing `Rc` to `MyUserdata` to create `MyUserdataHander` then. Alternalively you can store temporary values in Registry and create via [Lua::create_registry_value](https://docs.rs/mlua/0.6.2/mlua/struct.Lua.html#method.create_registry_value). [RegistryKey](https://docs.rs/mlua/0.6.2/mlua/prelude/struct.LuaRegistryKey.html) has `Drop` implemented...

I need to think about it. Not only `into_function` is needed, but apparenly a way to call functions/methods on arbitrary userdata. Also, `into_function` seems too optimistic. There are other functionality...

It's quite interesting question. Mostly because In Lua 5.1/JIT [lua_pushcfunction](https://www.lua.org/manual/5.1/manual.html#lua_pushcfunction) api call can trigger memory errors. Our protection mechanism to intercept Lua exceptions heavy relies on resilient `lua_pushcfunction` call. There...

> maybe I should use unsafe rust to call luajit c api directly it does not matter actually, you would get crash unless wrap it to [`lua_cpcall`](https://www.lua.org/manual/5.1/manual.html#lua_cpcall).