rust-lua53
rust-lua53 copied to clipboard
jcmoyer
Lua 5.3 bindings for Rust
Hi, I want to implement support for `ToLua` for `T:Serialze` from serde. So you can `lua_push` just about anything :) The problem I encountered is: ``` error[E0119]: conflicting implementations of...
I ran into this problem while trying to reproduce issue #72 on Windows 7 64-bit. I'm using the latest build: ``` rustc 1.12.1 (d4f39402a 2016-10-19) cargo 0.13.0-nightly (109cb7c 2016-08-19) ```...
Current push declaration is: ```rust impl State { fn push(&mut self, value: T) } ``` But `ToLua` satisfied with the reference `&self` (it doesn't need to own the instance). ```rust...
Released 2017-01-12 Though I'm curious why you're vendoring lua...
[Rust conventions](http://doc.crates.io/build-script.html#-sys-packages) prescribe a crate boundary between raw FFI bindings (the `ffi` module, the buildscript, and the generated glue) and a higher-level (even if it still has some `unsafe`) Rust...
Hi, It would be useful to include some third-party Lua libraries like LuaFilesystem into an application using rust-lua53. Since it builds its own copy of Lua, is there a good...
_(Please forgive me for the wall of text. It is an interesting read, I promise.)_ I am currently investigating into using this crate in a multithreaded manner. In order to...
`&mut self` not required for `is_*`, most `to_*`, `check_*`, and `opt_*` functions, and some others.
The `is_*` functions do not modify state at all, and having that reflected in their signature makes matches easier. All of the `to_*`, `check_*`, and `opt_*` functions do not modify...
Rust uses `jemalloc` for binaries (if possible), but lua's states created with `luaL_newstate` uses default system allocator. Different allocation strategies makes memory management wild. What about to use `lua_newstate` directly...
Hi, I'm trying to work out how safe calling the error method is, for reporting problems back to Lua code. It causes longjmp to unwind past a Rust function, which...