Open SpaceManiac opened 8 years ago
I've been aware of this convention for a while, but I haven't had the time (or motivation honestly) to split the low level bits out of the library. I agree it would be a nice thing to do though, if for no other reason than to be following standard guidelines.
It would be useful, if for example someone wanted to implement a luajit backend for the crate.
Rust conventions 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 someunsafe
) Rust wrapper. The advantages of such a configuration are primarily:-sys
crate, which can act as a central, definitive logic for finding a library on the system or otherwise linking to it.-sys
crate rather than conflicting.See, for example, the
hlua
crate, which bundles alua52-sys
crate: https://github.com/tomaka/hlua (This) Actually, maybe some collaboration with tomaka is warranted, given that this other crate also specifies-sys
crate also bundles its Lua source without requiring a secondary download, a good idea IMO, but that is another issue.links = "lua"
.There isn't really any urgent need for this, but I wanted to get some discussion started.