diff options
author | kyren <kerriganw@gmail.com> | 2018-02-10 17:55:20 -0500 |
---|---|---|
committer | kyren <kerriganw@gmail.com> | 2018-02-10 17:55:20 -0500 |
commit | c3242add409dabaafaff20f98c90ea02b9c77c6c (patch) | |
tree | 8081d7b508372d9e6c65b80bb1cbaef1d97f1216 /README.md | |
parent | 20480ec88da771bd06ef60b046d2b1be750f1781 (diff) | |
download | mlua-c3242add409dabaafaff20f98c90ea02b9c77c6c.zip |
Update README for readability
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 14 |
1 files changed, 7 insertions, 7 deletions
@@ -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: |