admin/mlua-rs-mlua
1
0
Fork 0
mirror of https://github.com/mlua-rs/mlua synced 2026-06-08 16:05:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README for readability

Browse Source
This commit is contained in:
kyren
2018-02-10 17:55:20 -05:00
parent 20480ec88d
commit c3242add40
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+7 -7
View File
@@ -13,13 +13,13 @@ as possible, while also being completely safe.
`rlua` is designed around "registry handles" to values inside the Lua state.
This means that when you get a type like `rlua::Table` or `rlua::Function` in
Rust, what you actually hold is an integer key into the Lua registry. This is
also different from the bare Lua C API, where you create tables / functions on
the Lua stack and must be aware of their location. This is also similar to how
other Lua bindings systems like [Selene](https://github.com/jeremyong/Selene)
for C++ work, but it means that using `rlua` may be slightly slower than what
you could conceivably write using the C API. This is done for reasons of safety
and flexibility, and to prevent the user of `rlua` from having to be aware of
the Lua stack at all.
different from the bare Lua C API, where you create tables / functions on the
Lua stack and must be aware of their stack location. This is also similar to
how other Lua bindings systems like
[Selene](https://github.com/jeremyong/Selene) for C++ work, but it means that
using `rlua` may be slightly slower than what you could conceivably write using
the C API. The reasons for this design are safety and flexibility, and to
prevent the user of `rlua` from having to be aware of the Lua stack at all.
There are currently a few missing pieces of this API: