Small README clarification
This commit is contained in:
parent
61236e685f
commit
f94037856a
11
README.md
11
README.md
|
@ -77,11 +77,12 @@ There are some caveats to the panic / abort guarantee, however:
|
|||
memory.
|
||||
* The internal Lua allocator is set to use `realloc` from `libc`, but it is
|
||||
wrapped in such a way that OOM errors are guaranteed to *abort*. This is
|
||||
not currently such a big deal, as this matches the behavior of Rust itself.
|
||||
This allows the internals of `rlua` to, in certain cases, call 'm' Lua C API
|
||||
functions with the garbage collector disabled and know that these cannot
|
||||
error. Eventually, `rlua` will support memory limits on scripts, and those
|
||||
memory limits will cause regular memory errors rather than OOM aborts.
|
||||
not currently such a huge deal outside of untrusted scripts, as this matches
|
||||
the behavior of Rust itself. Doing this allows the internals of `rlua` to,
|
||||
in certain cases, call 'm' Lua C API functions with the garbage collector
|
||||
disabled and know that these cannot error. Eventually, `rlua` will support
|
||||
memory limits on scripts, and those memory limits will cause regular memory
|
||||
errors rather than OOM aborts.
|
||||
|
||||
Yet another goal of the library is to, in all cases, safely handle panics
|
||||
generated by Rust callbacks. Panic unwinds in Rust callbacks should currently
|
||||
|
|
Loading…
Reference in New Issue